CIHealth
<
Single Day: Jun 11▾
Last 7 Days Weekly: Jun 8 - Jun 14 Sprint: Jun 8 - Jun 21 Single Day: Jun 11
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 5 · Failures matched: 17 · Total runs: 5 · Runs affected: 5

Failure patternThe canonical description of a recurring CI failure, extracted and normalized from raw logs.Failed atThe stage of the job run where this failure occurred: 'provision' (environment setup, DEV only), 'e2e' (test suite execution), or 'other' (CI infrastructure issues that did not produce a failure pattern).Number of distinct job runs where this failure pattern was detected.Percentage of all job runs in this environment affected by this failure pattern during the selected window.Classification of this failure pattern: Regression (likely caused by a specific PR), Flake (intermittent failure spread across days), Noise (low-quality or generic pattern), or Indeterminate.TrendShows daily activity for this failure pattern in a trailing window anchored to the selected end date. The sparkline covers at least 7 days and at most 14 days, depending on the current window size.Also inOther environments where the same failure pattern was also detected during the selected window.
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)
e2e480.00%4 of 5 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)Show trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 7none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-vfp6gc" for cluster "cluster-candidate-4-22-vfp6gc"
Unexpected error:
    <*fmt.wrapErrors | 0xc00111b320>: 
    failed to create NodePool np-vfp6gc, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-vfp6gc in resource group rg-candidate-4-22-k7jr2t, error: failed waiting for nodepool="np-vfp6gc" for cluster "cluster-candidate-4-22-vfp6gc" in resourcegroup="rg-candidate-4-22-k7jr2t" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-vfp6gc" for cluster "cluster-candidate-4-22-vfp6gc"
Unexpected error:
    <*fmt.wrapErrors | 0xc00111b320>: 
    failed to create NodePool np-vfp6gc, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-vfp6gc in resource group rg-candidate-4-22-k7jr2t, error: failed waiting for nodepool="np-vfp6gc" for cluster "cluster-candidate-4-22-vfp6gc" in resourcegroup="rg-candidate-4-22-k7jr2t" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-xxwcnw" for cluster "cluster-candidate-4-21-xxwcnw"
Unexpected error:
    <*fmt.wrapErrors | 0xc000c0d7a0>: 
    failed to create NodePool np-xxwcnw, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-xxwcnw in resource group rg-candidate-4-21-bm2dvr, error: failed waiting for nodepool="np-xxwcnw" for cluster "cluster-candidate-4-21-xxwcnw" in resourcegroup="rg-candidate-4-21-bm2dvr" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-xxwcnw" for cluster "cluster-candidate-4-21-xxwcnw"
Unexpected error:
    <*fmt.wrapErrors | 0xc000c0d7a0>: 
    failed to create NodePool np-xxwcnw, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-xxwcnw in resource group rg-candidate-4-21-bm2dvr, error: failed waiting for nodepool="np-xxwcnw" for cluster "cluster-candidate-4-21-xxwcnw" in resourcegroup="rg-candidate-4-21-bm2dvr" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-bc29t2" for cluster "cluster-candidate-4-21-bc29t2"
Unexpected error:
    <*fmt.wrapErrors | 0xc001422bd0>: 
    failed to create NodePool np-bc29t2, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-bc29t2 in resource group rg-candidate-4-21-zckkfx, error: failed waiting for nodepool="np-bc29t2" for cluster "cluster-candidate-4-21-bc29t2" in resourcegroup="rg-candidate-4-21-zckkfx" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-bc29t2" for cluster "cluster-candidate-4-21-bc29t2"
Unexpected error:
    <*fmt.wrapErrors | 0xc001422bd0>: 
    failed to create NodePool np-bc29t2, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-bc29t2 in resource group rg-candidate-4-21-zckkfx, error: failed waiting for nodepool="np-bc29t2" for cluster "cluster-candidate-4-21-bc29t2" in resourcegroup="rg-candidate-4-21-zckkfx" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (3)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.213
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.202
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.222
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2065210211181793280
n/a2065062586193285120
n/a2064941763205795840
n/a2064866707712774144
timeout during CreateHCPClusterAndWait; context deadline exceeded
full failure pattern:
timeout during CreateHCPClusterAndWait; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)
e2e360.00%3 of 5 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 5none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-5-0-wwmkpj/cluster-nightly-5-0-vh6qwq should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc001262480>: 
    failed waiting for cluster="cluster-nightly-5-0-vh6qwq" in resourcegroup="rg-nightly-5-0-wwmkpj" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-5-0-vh6qwq in resource group rg-nightly-5-0-wwmkpj, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-5-0-wwmkpj/cluster-nightly-5-0-vh6qwq should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc001262480>: 
    failed waiting for cluster="cluster-nightly-5-0-vh6qwq" in resourcegroup="rg-nightly-5-0-wwmkpj" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-5-0-vh6qwq in resource group rg-nightly-5-0-wwmkpj, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-4-23-jvdz4s/cluster-nightly-4-23-h8bmck should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0012ef830>: 
    failed waiting for cluster="cluster-nightly-4-23-h8bmck" in resourcegroup="rg-nightly-4-23-jvdz4s" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-h8bmck in resource group rg-nightly-4-23-jvdz4s, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-4-23-jvdz4s/cluster-nightly-4-23-h8bmck should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0012ef830>: 
    failed waiting for cluster="cluster-nightly-4-23-h8bmck" in resourcegroup="rg-nightly-4-23-jvdz4s" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-h8bmck in resource group rg-nightly-4-23-jvdz4s, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-4-23-tgndsp/cluster-nightly-4-23-sxpl48 should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0011aa810>: 
    failed waiting for cluster="cluster-nightly-4-23-sxpl48" in resourcegroup="rg-nightly-4-23-tgndsp" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-sxpl48 in resource group rg-nightly-4-23-tgndsp, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-4-23-tgndsp/cluster-nightly-4-23-sxpl48 should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0011aa810>: 
    failed waiting for cluster="cluster-nightly-4-23-sxpl48" in resourcegroup="rg-nightly-4-23-tgndsp" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-sxpl48 in resource group rg-nightly-4-23-tgndsp, error: context deadline exceeded
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.233
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.02
Affected runs (3)
Date (UTC)Associated PRProw job
n/a2065210211181793280
n/a2065062586193285120
n/a2064866707712774144
failed to cleanup resource group: at least one HCP cluster <cluster> to delete: failed waiting for hcpcluster="<cluster>" in resourcegroup="<resource-group>" to finish deleting: c...
full failure pattern:
failed to cleanup resource group: at least one HCP cluster <cluster> to delete: failed waiting for hcpcluster="<cluster>" in resourcegroup="<resource-group>" to finish deleting: context canceled
Signal: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)
e2e120.00%1 of 5 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 3none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:282] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc000d36660>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="cluster-np-labels-taints" in resourcegroup="rg-np-labels-taints-mdzh4m" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:282] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc000d36660>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="cluster-np-labels-taints" in resourcegroup="rg-np-labels-taints-mdzh4m" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:282] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc000caa390>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="np-drain-timeout-and-upgrade-nk7mdh" in resourcegroup="rg-np-drain-timeout-and-upgrade-nk7mdh-z5twvm" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:282] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc000caa390>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="np-drain-timeout-and-upgrade-nk7mdh" in resourcegroup="rg-np-drain-timeout-and-upgrade-nk7mdh-z5twvm" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:282] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc001678198>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="ephemeral-disk" in resourcegroup="ephemeral-osdisk-7ltfqs" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:282] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc001678198>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="ephemeral-disk" in resourcegroup="ephemeral-osdisk-7ltfqs" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
Contributing tests (3)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to update node pool labels and taints1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should update NodeDrainTimeoutMinutes and upgrade a nodepool1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelNodepool Ephemeral OS Disk should create a nodepool with ephemeral OS disk when autoRepair is enabled1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2064866707712774144
client rate limiter Wait returned an error: context deadline exceeded
full failure pattern:
client rate limiter Wait returned an error: context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)
e2e120.00%1 of 5 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)Show trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:190]: failed to verify nodes are Ready with Cilium CNI for cluster "cilium-cluster"
Unexpected error:
    <*errors.joinError | 0xc001081098>: 
    VerifyNodesReady failed: no nodes found in the cluster
    VerifyCiliumOperational failed: not all pods in kube-system namespace are running: failed to list pods in kube-system namespace: client rate limiter Wait returned an error: context deadline exceeded
    failed to create NodePool cilium-np, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool cilium-np in resource group complex-cilium-kv-b248kl, error: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-b248kl" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:190]: failed to verify nodes are Ready with Cilium CNI for cluster "cilium-cluster"
Unexpected error:
    <*errors.joinError | 0xc001081098>: 
    VerifyNodesReady failed: no nodes found in the cluster
    VerifyCiliumOperational failed: not all pods in kube-system namespace are running: failed to list pods in kube-system namespace: client rate limiter Wait returned an error: context deadline exceeded
    failed to create NodePool cilium-np, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool cilium-np in resource group complex-cilium-kv-b248kl, error: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-b248kl" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2064941763205795840
ERROR CODE: InvalidRequestContent; detail message no upgrade path found from 4.21.15 to 4.22.0: no reachable versions in target minor and no gateway version in current minor; prov...
full failure pattern:
ERROR CODE: InvalidRequestContent; detail message no upgrade path found from 4.21.15 to 4.22.0: no reachable versions in target minor and no gateway version in current minor; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e120.00%1 of 5 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:215]: failed to trigger y-stream upgrade of cluster "cp-ystream-upgrade-4-22-t6zgnn" to 4.22
Unexpected error:
    <*fmt.wrapError | 0xc000daa9a0>: 
    failed waiting for hcpCluster="cp-ystream-upgrade-4-22-t6zgnn" in resourcegroup="rg-cp-ystream-upgrade-4-22-65ltw8" to finish updating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/2b654c62-7bae-4f51-828c-b10da7a88688
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/2b654c62-7bae-4f51-828c-b10da7a88688",
      "name": "2b654c62-7bae-4f51-828c-b10da7a88688",
      "status": "Failed",
      "startTime": "2026-06-11T20:21:45.858985705Z",
      "endTime": "2026-06-11T20:22:38.89726274Z",
      "error": {
        "code": "InvalidRequestContent",
        "message": "no upgrade path found from 4.21.15 to 4.22.0: no reachable versions in target minor and no gateway version in current minor"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:215]: failed to trigger y-stream upgrade of cluster "cp-ystream-upgrade-4-22-t6zgnn" to 4.22
Unexpected error:
    <*fmt.wrapError | 0xc000daa9a0>: 
    failed waiting for hcpCluster="cp-ystream-upgrade-4-22-t6zgnn" in resourcegroup="rg-cp-ystream-upgrade-4-22-65ltw8" to finish updating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/2b654c62-7bae-4f51-828c-b10da7a88688
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/2b654c62-7bae-4f51-828c-b10da7a88688",
      "name": "2b654c62-7bae-4f51-828c-b10da7a88688",
      "status": "Failed",
      "startTime": "2026-06-11T20:21:45.858985705Z",
      "endTime": "2026-06-11T20:22:38.89726274Z",
      "error": {
        "code": "InvalidRequestContent",
        "message": "no upgrade path found from 4.21.15 to 4.22.0: no reachable versions in target minor and no gateway version in current minor"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to successfully upgrade control plane minor version from 4.21 minor to 4.22 minor1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2065155767597535232