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: PROD

Failure patterns: 6 · Failures matched: 17 · Total runs: 9 · Runs affected: 2

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)
e2e111.11%1 of 9 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: 12none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:89]: Unexpected error:
    <*fmt.wrapErrors | 0xc0015b8630>: 
    failed to create HCP cluster cx-rg-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-ltj7bm, error: failed waiting for cluster="cx-rg-hcp-cluster" in resourcegroup="cx-rg-cluster-ltj7bm" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-ltj7bm, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:89]: Unexpected error:
    <*fmt.wrapErrors | 0xc0015b8630>: 
    failed to create HCP cluster cx-rg-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-ltj7bm, error: failed waiting for cluster="cx-rg-hcp-cluster" in resourcegroup="cx-rg-cluster-ltj7bm" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-ltj7bm, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:130]: Unexpected error:
    <*fmt.wrapErrors | 0xc0012051a0>: 
    failed to create HCP cluster np-version-upgrade-cluster-lflsk8, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-version-upgrade-cluster-lflsk8 in resource group rg-np-version-upgrade-lflsk8-kmghrh, error: failed waiting for cluster="np-version-upgrade-cluster-lflsk8" in resourcegroup="rg-np-version-upgrade-lflsk8-kmghrh" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-version-upgrade-cluster-lflsk8 in resource group rg-np-version-upgrade-lflsk8-kmghrh, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:130]: Unexpected error:
    <*fmt.wrapErrors | 0xc0012051a0>: 
    failed to create HCP cluster np-version-upgrade-cluster-lflsk8, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-version-upgrade-cluster-lflsk8 in resource group rg-np-version-upgrade-lflsk8-kmghrh, error: failed waiting for cluster="np-version-upgrade-cluster-lflsk8" in resourcegroup="rg-np-version-upgrade-lflsk8-kmghrh" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-version-upgrade-cluster-lflsk8 in resource group rg-np-version-upgrade-lflsk8-kmghrh, 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 | 0xc000d98e10>: 
    failed to create HCP cluster cluster-zstream-4-21-fq9zrm, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-21-fq9zrm in resource group rg-zstream-upgrade-4-21-4cpjp2, error: failed waiting for cluster="cluster-zstream-4-21-fq9zrm" in resourcegroup="rg-zstream-upgrade-4-21-4cpjp2" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-21-fq9zrm in resource group rg-zstream-upgrade-4-21-4cpjp2, 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 | 0xc000d98e10>: 
    failed to create HCP cluster cluster-zstream-4-21-fq9zrm, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-21-fq9zrm in resource group rg-zstream-upgrade-4-21-4cpjp2, error: failed waiting for cluster="cluster-zstream-4-21-fq9zrm" in resourcegroup="rg-zstream-upgrade-4-21-4cpjp2" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-21-fq9zrm in resource group rg-zstream-upgrade-4-21-4cpjp2, error: context deadline exceeded
    ...
occurred
Contributing tests (12)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP1
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
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create an HCP cluster and manage ImageDigestMirrors1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create an HCP cluster then delete it by deleting the customer resource group1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create an HCP cluster with custom autoscaling1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create node pools with ARM64-based VMs1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to successfully upgrade control plane minor version from 4.20 minor to 4.21 minor1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.21.zLatest1
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.191
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
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.211
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2052503972110929920
Cluster should become ready within 45 minutes
full failure pattern:
Cluster should become ready within 45 minutes
Signal: IndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)
e2e111.11%1 of 9 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 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: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:162]: Timed out after 2700.001s.
Cluster should become ready within 45 minutes
Expected
    <bool>: ...
to be true
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:162]: Timed out after 2700.001s.
Cluster should become ready within 45 minutes
Expected
    <bool>: ...
to be true
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2052503972110929920
context deadline exceeded
full failure pattern:
context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)
e2e111.11%1 of 9 job runs affectedIndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)Show trend detailsMay 1: 0 · May 2: 0 · May 3: 0 · May 4: 1 · May 5: 0 · May 6: 0 · May 7: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:139]: Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:139]: Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2052503972110929920
ERROR CODE: AuthenticationFailed; context ; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: AuthenticationFailed; context ; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e111.11%1 of 9 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: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:108]: Unexpected error:
    <*fmt.wrapError | 0xc000e04260>: 
    failed waiting for cluster="private-kv-cluster" in resourcegroup="private-keyvault-jc8js6" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/eastus2/hcpOperationStatuses/1555f87d-c77a-446e-9812-a74076b41278
    --------------------------------------------------------------------------------
    RESPONSE 401: 401 Unauthorized
    ERROR CODE: AuthenticationFailed
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "AuthenticationFailed",
        "message": "Authentication failed."
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:108]: Unexpected error:
    <*fmt.wrapError | 0xc000e04260>: 
    failed waiting for cluster="private-kv-cluster" in resourcegroup="private-keyvault-jc8js6" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/eastus2/hcpOperationStatuses/1555f87d-c77a-446e-9812-a74076b41278
    --------------------------------------------------------------------------------
    RESPONSE 401: 401 Unauthorized
    ERROR CODE: AuthenticationFailed
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "AuthenticationFailed",
        "message": "Authentication failed."
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2052503972110929920
dial tcp: lookup console-openshift-console
full failure pattern:
dial tcp: lookup console-openshift-console
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e111.11%1 of 9 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: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:153]: Timed out after 240.001s.
expect ingress certificate to be signed by a trusted Azure CA
Expected success, but got an error:
    <*net.OpError | 0xc0008fa690>: 
    dial tcp: lookup console-openshift-console.apps.aro.c1m2s6r4u2z7j9m.cpvn.centralindia.aroapp-hcp.io on 172.30.0.10:53: no such host
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:153]: Timed out after 240.001s.
expect ingress certificate to be signed by a trusted Azure CA
Expected success, but got an error:
    <*net.OpError | 0xc0008fa690>: 
    dial tcp: lookup console-openshift-console.apps.aro.c1m2s6r4u2z7j9m.cpvn.centralindia.aroapp-hcp.io on 172.30.0.10:53: no such host
    ...
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should create an HCP cluster and validate TLS certificates1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2052369690725978112
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 1 prior week(s); active 1 day(s)
e2e111.11%1 of 9 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 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: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc0011a2138>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="ea-cluster" in resourcegroup="external-auth-cluster-hkqvxb" 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:249] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc0011a2138>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="ea-cluster" in resourcegroup="external-auth-cluster-hkqvxb" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create a cluster with an external auth config and get the external auth config1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2052503972110929920