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

Environment: PROD

Failure patterns: 5 · Failures matched: 9 · Total runs: 12 · Runs affected: 6

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.
client rate limiter Wait returned an error: context deadline exceeded
full failure pattern:
client rate limiter Wait returned an error: context deadline exceeded
Signal: FlakeSignal: Flake — present in 2 prior week(s); spread across 4 days
e2e18.33%1 of 12 job runs affectedFlakeSignal: Flake — present in 2 prior week(s); spread across 4 daysShow trend detailsJun 12: 0 · Jun 13: 2 · Jun 14: 0 · Jun 15: 1 · Jun 16: 2 · Jun 17: 0 · Jun 18: 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 | 0xc000b508d0>: 
    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-mgjdp6, error: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-mgjdp6" 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 | 0xc000b508d0>: 
    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-mgjdp6, error: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-mgjdp6" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-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/a2067641305726455808
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 3 prior week(s); active 1 day(s)
e2e325.00%3 of 12 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsJun 12: 0 · Jun 13: 0 · Jun 14: 0 · Jun 15: 0 · Jun 16: 0 · Jun 17: 0 · Jun 18: 3none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:136]: failed to create node pool "np-1" for private keyvault cluster "private-kv-cluster"
Unexpected error:
    <*fmt.wrapErrors | 0xc0009e83c0>: 
    failed to create NodePool np-1, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-6m9cck, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-6m9cck" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:136]: failed to create node pool "np-1" for private keyvault cluster "private-kv-cluster"
Unexpected error:
    <*fmt.wrapErrors | 0xc0009e83c0>: 
    failed to create NodePool np-1, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-6m9cck, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-6m9cck" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_ephemeral_osdisk.go:135]: failed to create nodepool ephemeral-np with ephemeral OS disk
Unexpected error:
    <*fmt.wrapErrors | 0xc0015c0990>: 
    failed to create NodePool ephemeral-np, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool ephemeral-np in resource group ephemeral-osdisk-fkxsj5, error: failed waiting for nodepool="ephemeral-np" for cluster "ephemeral-disk" in resourcegroup="ephemeral-osdisk-fkxsj5" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_ephemeral_osdisk.go:135]: failed to create nodepool ephemeral-np with ephemeral OS disk
Unexpected error:
    <*fmt.wrapErrors | 0xc0015c0990>: 
    failed to create NodePool ephemeral-np, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool ephemeral-np in resource group ephemeral-osdisk-fkxsj5, error: failed waiting for nodepool="ephemeral-np" for cluster "ephemeral-disk" in resourcegroup="ephemeral-osdisk-fkxsj5" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:159]: failed to create node pool "np-c5q44t" for cluster "cluster-candidate-4-21-c5q44t"
Unexpected error:
    <*fmt.wrapErrors | 0xc0009f06c0>: 
    failed to create NodePool np-c5q44t, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-c5q44t in resource group rg-candidate-4-21-kztrgv, error: failed waiting for nodepool="np-c5q44t" for cluster "cluster-candidate-4-21-c5q44t" in resourcegroup="rg-candidate-4-21-kztrgv" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:159]: failed to create node pool "np-c5q44t" for cluster "cluster-candidate-4-21-c5q44t"
Unexpected error:
    <*fmt.wrapErrors | 0xc0009f06c0>: 
    failed to create NodePool np-c5q44t, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-c5q44t in resource group rg-candidate-4-21-kztrgv, error: failed waiting for nodepool="np-c5q44t" for cluster "cluster-candidate-4-21-c5q44t" in resourcegroup="rg-candidate-4-21-kztrgv" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (3)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.211
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelNodepool Ephemeral OS Disk should create a nodepool with ephemeral OS disk when autoRepair is enabled1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallel-ocp-nightlyCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
Affected runs (3)
Date (UTC)Associated PRProw job
n/a2067744257157894144
n/a2067643701898776576
n/a2067598465302532096
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)
e2e325.00%3 of 12 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJun 12: 0 · Jun 13: 0 · Jun 14: 0 · Jun 15: 0 · Jun 16: 0 · Jun 17: 0 · Jun 18: 3none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_list_and_verify.go:83]: failed to create HCP cluster for external auth list test
Unexpected error:
    <*fmt.wrapErrors | 0xc0012cf560>: 
    failed to create HCP cluster ea-listdw56tc, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster ea-listdw56tc in resource group ea-list-pfrc2w, error: failed waiting for cluster="ea-listdw56tc" in resourcegroup="ea-list-pfrc2w" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster ea-listdw56tc in resource group ea-list-pfrc2w, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_list_and_verify.go:83]: failed to create HCP cluster for external auth list test
Unexpected error:
    <*fmt.wrapErrors | 0xc0012cf560>: 
    failed to create HCP cluster ea-listdw56tc, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster ea-listdw56tc in resource group ea-list-pfrc2w, error: failed waiting for cluster="ea-listdw56tc" in resourcegroup="ea-list-pfrc2w" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster ea-listdw56tc in resource group ea-list-pfrc2w, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-5-0-swwhjt/cluster-candidate-5-0-frc9tc should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0006eade0>: 
    failed to create HCP cluster cluster-candidate-5-0-frc9tc, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-frc9tc in resource group rg-candidate-5-0-swwhjt, error: failed waiting for cluster="cluster-candidate-5-0-frc9tc" in resourcegroup="rg-candidate-5-0-swwhjt" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-frc9tc in resource group rg-candidate-5-0-swwhjt, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-5-0-swwhjt/cluster-candidate-5-0-frc9tc should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0006eade0>: 
    failed to create HCP cluster cluster-candidate-5-0-frc9tc, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-frc9tc in resource group rg-candidate-5-0-swwhjt, error: failed waiting for cluster="cluster-candidate-5-0-frc9tc" in resourcegroup="rg-candidate-5-0-swwhjt" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-frc9tc in resource group rg-candidate-5-0-swwhjt, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_cluster_create.go:88]: failed to create HCP cluster with image registry disabled
Unexpected error:
    <*fmt.wrapErrors | 0xc00144c750>: 
    failed to create HCP cluster disabled-image-registry-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-5b4j95, error: failed waiting for cluster="disabled-image-registry-hcp-cluster" in resourcegroup="disabled-image-registry-5b4j95" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-5b4j95, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_cluster_create.go:88]: failed to create HCP cluster with image registry disabled
Unexpected error:
    <*fmt.wrapErrors | 0xc00144c750>: 
    failed to create HCP cluster disabled-image-registry-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-5b4j95, error: failed waiting for cluster="disabled-image-registry-hcp-cluster" in resourcegroup="disabled-image-registry-5b4j95" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-5b4j95, error: context deadline exceeded
    ...
occurred
Contributing tests (3)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.01
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create an HCP cluster with Image Registry not present1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster1
Affected runs (3)
Date (UTC)Associated PRProw job
n/a2067643701898776576
n/a2067524854185201664
n/a2067472693011156992
ERROR CODE: DeploymentNotFound
full failure pattern:
ERROR CODE: DeploymentNotFound
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e18.33%1 of 12 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 12: 0 · Jun 13: 0 · Jun 14: 0 · Jun 15: 0 · Jun 16: 0 · Jun 17: 0 · Jun 18: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:92]: failed to create customer resources for z-stream cluster "cluster-zstream-4-20-fw7f2d"
Unexpected error:
    <*fmt.wrapError | 0xc000f9b3c0>: 
    failed to create managed identities: failed to create managed identities: failed waiting for deployment "mi-cluster-zstream-4-20-fw7f2d-k89rj5" at subscription scope to finish: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.Resources/deployments/mi-cluster-zstream-4-20-fw7f2d-k89rj5/operationStatuses/08584198113386810784
    --------------------------------------------------------------------------------
    RESPONSE 404: 404 Not Found
    ERROR CODE: DeploymentNotFound
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "DeploymentNotFound",
        "message": "Deployment 'mi-cluster-zstream-4-20-fw7f2d-k89rj5' could not be found."
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:92]: failed to create customer resources for z-stream cluster "cluster-zstream-4-20-fw7f2d"
Unexpected error:
    <*fmt.wrapError | 0xc000f9b3c0>: 
    failed to create managed identities: failed to create managed identities: failed waiting for deployment "mi-cluster-zstream-4-20-fw7f2d-k89rj5" at subscription scope to finish: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.Resources/deployments/mi-cluster-zstream-4-20-fw7f2d-k89rj5/operationStatuses/08584198113386810784
    --------------------------------------------------------------------------------
    RESPONSE 404: 404 Not Found
    ERROR CODE: DeploymentNotFound
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "DeploymentNotFound",
        "message": "Deployment 'mi-cluster-zstream-4-20-fw7f2d-k89rj5' could not be found."
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.201
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2067598465302532096
Should fail with EOF error indicating blocked connection
full failure pattern:
Should fail with EOF error indicating blocked connection
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e18.33%1 of 12 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 12: 0 · Jun 13: 0 · Jun 14: 0 · Jun 15: 0 · Jun 16: 0 · Jun 17: 0 · Jun 18: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:190]: Should fail with EOF error indicating blocked connection
Expected
    <string>: ...
to contain substring
    <string>: ...
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:190]: Should fail with EOF error indicating blocked connection
Expected
    <string>: ...
to contain substring
    <string>: ...
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallel-ocp-nightlyAuthorized CIDRs Connectivity should allow API access only from authorized VM IP1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2067744257157894144