CIHealth
<
Single Day: Jun 1▾
Last 7 Days Weekly: Jun 1 - Jun 7 Sprint: May 25 - Jun 7 Single Day: Jun 1
Custom time window
> Reset
View JSON API

Environment: STG

Failure patterns: 2 · Failures matched: 3 · Total runs: 1 · Runs affected: 1

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: FlakeSignal: Flake — present in 4 prior week(s); spread across 3 days
e2e1100.00%1 of 1 job runs affectedFlakeSignal: Flake — present in 4 prior week(s); spread across 3 daysShow trend detailsMay 26: 0 · May 27: 0 · May 28: 2 · May 29: 0 · May 30: 0 · May 31: 2 · Jun 1: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:127]: Swift cluster rg-nightly-4-23-rjlvjr/cluster-nightly-4-23-ngq48p should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0006d4060>: 
    failed waiting for cluster="cluster-nightly-4-23-ngq48p" in resourcegroup="rg-nightly-4-23-rjlvjr" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-ngq48p in resource group rg-nightly-4-23-rjlvjr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:127]: Swift cluster rg-nightly-4-23-rjlvjr/cluster-nightly-4-23-ngq48p should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0006d4060>: 
    failed waiting for cluster="cluster-nightly-4-23-ngq48p" in resourcegroup="rg-nightly-4-23-rjlvjr" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-ngq48p in resource group rg-nightly-4-23-rjlvjr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/idms_lifecycle.go:112]: failed to create HCP cluster with ImageDigestMirrors
Unexpected error:
    <*fmt.wrapErrors | 0xc0016a60c0>: 
    failed to create HCP cluster idms-e2e-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster idms-e2e-hcp-cluster in resource group idms-cqrckd, error: failed waiting for cluster="idms-e2e-hcp-cluster" in resourcegroup="idms-cqrckd" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster idms-e2e-hcp-cluster in resource group idms-cqrckd, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/idms_lifecycle.go:112]: failed to create HCP cluster with ImageDigestMirrors
Unexpected error:
    <*fmt.wrapErrors | 0xc0016a60c0>: 
    failed to create HCP cluster idms-e2e-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster idms-e2e-hcp-cluster in resource group idms-cqrckd, error: failed waiting for cluster="idms-e2e-hcp-cluster" in resourcegroup="idms-cqrckd" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster idms-e2e-hcp-cluster in resource group idms-cqrckd, error: context deadline exceeded
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.231
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster and manage ImageDigestMirrors1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2061266582377598976
add password after 2 attempts; last attempt error: error status code received from the API; polling error: error status code received from the API
full failure pattern:
add password after 2 attempts; last attempt error: error status code received from the API; polling error: error status code received from the API
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e1100.00%1 of 1 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 26: 0 · May 27: 0 · May 28: 0 · May 29: 0 · May 30: 0 · May 31: 0 · Jun 1: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_create.go:132]: failed to add password to app registration
Unexpected error:
    <*fmt.wrapErrors | 0xc00038bc20>: 
    add password after 2 attempts; last attempt error: error status code received from the API; polling error: error status code received from the API
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_create.go:132]: failed to add password to app registration
Unexpected error:
    <*fmt.wrapErrors | 0xc00038bc20>: 
    add password after 2 attempts; last attempt error: error status code received from the API; polling error: error status code received from the API
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-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/a2061266582377598976