CIHealth
<
Single Day: Apr 21▾
Last 7 Days Weekly: Apr 20 - Apr 26 Sprint: Apr 13 - Apr 26 Single Day: Apr 21
Custom time window
> Reset
View JSON API

Environment: PROD

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 detailsApr 15: 0 · Apr 16: 0 · Apr 17: 0 · Apr 18: 0 · Apr 19: 0 · Apr 20: 0 · Apr 21: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:115]: Unexpected error:
    <*fmt.wrapErrors | 0xc000d50bd0>: 
    failed to create HCP cluster cluster-candidate-4-21-rhss9q, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-candidate-4-21-rhss9q in resource group rg-candidate-4-21-xhzp5g, error: failed waiting for cluster="cluster-candidate-4-21-rhss9q" in resourcegroup="rg-candidate-4-21-xhzp5g" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-candidate-4-21-rhss9q in resource group rg-candidate-4-21-xhzp5g, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:115]: Unexpected error:
    <*fmt.wrapErrors | 0xc000d50bd0>: 
    failed to create HCP cluster cluster-candidate-4-21-rhss9q, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-candidate-4-21-rhss9q in resource group rg-candidate-4-21-xhzp5g, error: failed waiting for cluster="cluster-candidate-4-21-rhss9q" in resourcegroup="rg-candidate-4-21-xhzp5g" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-candidate-4-21-rhss9q in resource group rg-candidate-4-21-xhzp5g, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.211
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2046408704101715968