CIHealth
<
Single Day: May 23▾
Last 7 Days Weekly: May 18 - May 24 Sprint: May 11 - May 24 Single Day: May 23
Custom time window
> Reset
View JSON API

Environment: STG

Failure patterns: 1 · Failures matched: 1 · 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: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)
e2e1100.00%1 of 1 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsMay 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 0 · May 23: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:158]: failed to create HCP cluster "cp-ystream-upgrade-4-22-24644n" with install version 4.21.16
Unexpected error:
    <*fmt.wrapErrors | 0xc000aa96e0>: 
    failed to create HCP cluster cp-ystream-upgrade-4-22-24644n, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-22-24644n in resource group rg-cp-ystream-upgrade-4-22-xpdwqm, error: failed waiting for cluster="cp-ystream-upgrade-4-22-24644n" in resourcegroup="rg-cp-ystream-upgrade-4-22-xpdwqm" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-22-24644n in resource group rg-cp-ystream-upgrade-4-22-xpdwqm, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:158]: failed to create HCP cluster "cp-ystream-upgrade-4-22-24644n" with install version 4.21.16
Unexpected error:
    <*fmt.wrapErrors | 0xc000aa96e0>: 
    failed to create HCP cluster cp-ystream-upgrade-4-22-24644n, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-22-24644n in resource group rg-cp-ystream-upgrade-4-22-xpdwqm, error: failed waiting for cluster="cp-ystream-upgrade-4-22-24644n" in resourcegroup="rg-cp-ystream-upgrade-4-22-xpdwqm" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-22-24644n in resource group rg-cp-ystream-upgrade-4-22-xpdwqm, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-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/a2058004991464968192