CIHealth
<
Single Day: May 7▾
Last 7 Days Weekly: May 4 - May 10 Sprint: Apr 27 - May 10 Single Day: May 7
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 4 · Failures matched: 75 · Total runs: 6 · Runs affected: 3

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.
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)
e2e233.33%2 of 6 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsMay 1: 0 · May 2: 0 · May 3: 0 · May 4: 0 · May 5: 0 · May 6: 0 · May 7: 69none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_pullsecret.go:134]: Unexpected error:
    <*fmt.wrapErrors | 0xc000d50f90>: 
    failed to create HCP cluster pullsecret-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster pullsecret-hcp-cluster in resource group pullsecret-test-ndb9n4, error: failed waiting for cluster="pullsecret-hcp-cluster" in resourcegroup="pullsecret-test-ndb9n4" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster pullsecret-hcp-cluster in resource group pullsecret-test-ndb9n4, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_pullsecret.go:134]: Unexpected error:
    <*fmt.wrapErrors | 0xc000d50f90>: 
    failed to create HCP cluster pullsecret-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster pullsecret-hcp-cluster in resource group pullsecret-test-ndb9n4, error: failed waiting for cluster="pullsecret-hcp-cluster" in resourcegroup="pullsecret-test-ndb9n4" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster pullsecret-hcp-cluster in resource group pullsecret-test-ndb9n4, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:141]: Unexpected error:
    <*fmt.wrapErrors | 0xc0014ff350>: 
    failed to create HCP cluster cluster-zstream-4-19-zq9mbq, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-19-zq9mbq in resource group rg-zstream-upgrade-4-19-lt2snx, error: failed waiting for cluster="cluster-zstream-4-19-zq9mbq" in resourcegroup="rg-zstream-upgrade-4-19-lt2snx" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-19-zq9mbq in resource group rg-zstream-upgrade-4-19-lt2snx, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:141]: Unexpected error:
    <*fmt.wrapErrors | 0xc0014ff350>: 
    failed to create HCP cluster cluster-zstream-4-19-zq9mbq, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-19-zq9mbq in resource group rg-zstream-upgrade-4-19-lt2snx, error: failed waiting for cluster="cluster-zstream-4-19-zq9mbq" in resourcegroup="rg-zstream-upgrade-4-19-lt2snx" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-19-zq9mbq in resource group rg-zstream-upgrade-4-19-lt2snx, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:115]: Unexpected error:
    <*fmt.wrapErrors | 0xc0013e67b0>: 
    failed to create HCP cluster cluster-candidate-4-22-spnh6f, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-candidate-4-22-spnh6f in resource group rg-candidate-4-22-44hnbq, error: failed waiting for cluster="cluster-candidate-4-22-spnh6f" in resourcegroup="rg-candidate-4-22-44hnbq" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-candidate-4-22-spnh6f in resource group rg-candidate-4-22-44hnbq, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:115]: Unexpected error:
    <*fmt.wrapErrors | 0xc0013e67b0>: 
    failed to create HCP cluster cluster-candidate-4-22-spnh6f, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-candidate-4-22-spnh6f in resource group rg-candidate-4-22-44hnbq, error: failed waiting for cluster="cluster-candidate-4-22-spnh6f" in resourcegroup="rg-candidate-4-22-44hnbq" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-candidate-4-22-spnh6f in resource group rg-candidate-4-22-44hnbq, error: context deadline exceeded
    ...
occurred
Contributing tests (35)
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.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.212
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
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a HCP cluster and use cilium CNI plugin2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a cluster with an external auth config and get the external auth config2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled up to replica limits2
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 successfully2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster and custom node pool osDisk size2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster and manage ImageDigestMirrors2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster and manage pull secrets2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster then delete it by deleting the customer resource group2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster with Image Registry not present2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster with back-level version 4.192
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster with custom autoscaling2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create node pools with ARM64-based VMs2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to successfully upgrade control plane minor version from 4.20 minor to 4.21 minor2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to update node pool labels and taints2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to use workload identity via the cluster OIDC issuer URL2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should create an HCP cluster and validate TLS certificates2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should not be able to perform various invalid operations on cluster resources2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should not be able to reuse subnets and NSGs between clusters2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should respect cluster-wide node limits with nodepool autoscaling2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.21.zLatest2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should upgrade and update a nodepool from 4.21.z to 4.21.zLatest2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelHCP Nodepools GPU instances creates and deletes vm type NC4asT4v3 in a single cluster2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelNodepool Ephemeral OS Disk should create a nodepool with ephemeral OS disk when autoRepair is enabled2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.192
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.202
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.212
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelUpdate HCPOpenShiftCluster Negative creates a cluster and fails to update its name with a PATCH request2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelUpdate HCPOpenShiftCluster Positive creates a cluster and updates tags with a PATCH request2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.20.zLatest1
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2052271926398685184
n/a2052178744273014784
context deadline exceeded
full failure pattern:
context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 3 day(s)
e2e233.33%2 of 6 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 3 day(s)Show trend detailsMay 1: 0 · May 2: 0 · May 3: 0 · May 4: 1 · May 5: 0 · May 6: 3 · May 7: 2none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group2
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2052271926398685184
n/a2052178744273014784
Cluster should become ready within '20.000000' minutes
full failure pattern:
Cluster should become ready within '20.000000' minutes
Signal: IndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior history
e2e233.33%2 of 6 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior historyShow trend detailsMay 1: 0 · May 2: 0 · May 3: 0 · May 4: 0 · May 5: 0 · May 6: 3 · May 7: 2none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:162]: Timed out after 1200.001s.
Cluster should become ready within '20.000000' minutes
Expected
    <bool>: ...
to be true
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:162]: Timed out after 1200.001s.
Cluster should become ready within '20.000000' minutes
Expected
    <bool>: ...
to be true
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle2
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2052271926398685184
n/a2052178744273014784
ERROR CODE: LockContention; detail message Failed to acquire lock: timed out; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: LockContention; detail message Failed to acquire lock: timed out; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e116.67%1 of 6 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 1: 0 · May 2: 0 · May 3: 0 · May 4: 0 · May 5: 0 · May 6: 0 · May 7: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249]: Unexpected error:
    <*errors.joinError | 0xc0010ee2d0>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: DELETE https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/disabled-image-registry-5nshss/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/disabled-image-registry-hcp-cluster
    --------------------------------------------------------------------------------
    RESPONSE 503: 503 Service Unavailable
    ERROR CODE: LockContention
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "LockContention",
        "message": "Failed to acquire lock: timed out",
        "target": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249]: Unexpected error:
    <*errors.joinError | 0xc0010ee2d0>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: DELETE https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/disabled-image-registry-5nshss/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/disabled-image-registry-hcp-cluster
    --------------------------------------------------------------------------------
    RESPONSE 503: 503 Service Unavailable
    ERROR CODE: LockContention
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "LockContention",
        "message": "Failed to acquire lock: timed out",
        "target": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:144]: Unexpected error:
    <*fmt.wrapError | 0xc000e48460>: 
    failed to create NodePool gpu-np-1: failed starting nodepool creation "gpu-np-1" for cluster "cluster-gpu-np" in resourcegroup="rg-gpu-nodepool-NC4asT4v3-tvwrsk": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-gpu-nodepool-NC4asT4v3-tvwrsk/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-gpu-np/nodePools/gpu-np-1
    --------------------------------------------------------------------------------
    RESPONSE 503: 503 Service Unavailable
    ERROR CODE: LockContention
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "LockContention",
        "message": "Failed to acquire lock: timed out",
        "target": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:144]: Unexpected error:
    <*fmt.wrapError | 0xc000e48460>: 
    failed to create NodePool gpu-np-1: failed starting nodepool creation "gpu-np-1" for cluster "cluster-gpu-np" in resourcegroup="rg-gpu-nodepool-NC4asT4v3-tvwrsk": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-gpu-nodepool-NC4asT4v3-tvwrsk/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-gpu-np/nodePools/gpu-np-1
    --------------------------------------------------------------------------------
    RESPONSE 503: 503 Service Unavailable
    ERROR CODE: LockContention
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "LockContention",
        "message": "Failed to acquire lock: timed out",
        "target": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster with Image Registry not present1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelHCP Nodepools GPU instances creates and deletes vm type NC4asT4v3 in a single cluster1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2052459411028316160