CIHealth
<
Single Day: Jun 22▾
Last 7 Days Weekly: Jun 22 - Jun 28 Sprint: Jun 22 - Jul 5 Single Day: Jun 22
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 2 · Failures matched: 3 · Total runs: 6 · 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)
e2e233.33%2 of 6 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJun 16: 0 · Jun 17: 0 · Jun 18: 0 · Jun 19: 0 · Jun 20: 0 · Jun 21: 0 · Jun 22: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:102]: failed to create HCP cluster "cluster-zstream-4-22-5r22px" with version 4.22.0 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc001470090>: 
    failed to create HCP cluster cluster-zstream-4-22-5r22px, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-5r22px in resource group rg-zstream-upgrade-4-22-rqlnfc, error: failed waiting for cluster="cluster-zstream-4-22-5r22px" in resourcegroup="rg-zstream-upgrade-4-22-rqlnfc" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-5r22px in resource group rg-zstream-upgrade-4-22-rqlnfc, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:102]: failed to create HCP cluster "cluster-zstream-4-22-5r22px" with version 4.22.0 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc001470090>: 
    failed to create HCP cluster cluster-zstream-4-22-5r22px, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-5r22px in resource group rg-zstream-upgrade-4-22-rqlnfc, error: failed waiting for cluster="cluster-zstream-4-22-5r22px" in resourcegroup="rg-zstream-upgrade-4-22-rqlnfc" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-5r22px in resource group rg-zstream-upgrade-4-22-rqlnfc, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:102]: failed to create HCP cluster "cluster-zstream-4-22-fbcwzr" with version 4.22.0 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc001000360>: 
    failed to create HCP cluster cluster-zstream-4-22-fbcwzr, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-fbcwzr in resource group rg-zstream-upgrade-4-22-cnzr2b, error: failed waiting for cluster="cluster-zstream-4-22-fbcwzr" in resourcegroup="rg-zstream-upgrade-4-22-cnzr2b" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-fbcwzr in resource group rg-zstream-upgrade-4-22-cnzr2b, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:102]: failed to create HCP cluster "cluster-zstream-4-22-fbcwzr" with version 4.22.0 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc001000360>: 
    failed to create HCP cluster cluster-zstream-4-22-fbcwzr, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-fbcwzr in resource group rg-zstream-upgrade-4-22-cnzr2b, error: failed waiting for cluster="cluster-zstream-4-22-fbcwzr" in resourcegroup="rg-zstream-upgrade-4-22-cnzr2b" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-fbcwzr in resource group rg-zstream-upgrade-4-22-cnzr2b, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
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.222
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2068956060353302528
n/a2068856415081992192
VerifyCiliumConnectivityChecks failed: failed to create test resource from artifacts/cilium-connectivity-check-1.19.2/connectivity-check-internal.0014.yaml: Service "echo-b" is in...
full failure pattern:
VerifyCiliumConnectivityChecks failed: failed to create test resource from artifacts/cilium-connectivity-check-1.19.2/connectivity-check-internal.0014.yaml: Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31414: provided port is already
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 detailsJun 16: 0 · Jun 17: 0 · Jun 18: 0 · Jun 19: 0 · Jun 20: 0 · Jun 21: 0 · Jun 22: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cni_cilium.go:170]: failed to run simple web app and connectivity check app with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc0010e61f8>: 
    VerifyCiliumConnectivityChecks failed: failed to create test resource from artifacts/cilium-connectivity-check-1.19.2/connectivity-check-internal.0014.yaml: Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31414: provided port is already allocated
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cni_cilium.go:170]: failed to run simple web app and connectivity check app with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc0010e61f8>: 
    VerifyCiliumConnectivityChecks failed: failed to create test resource from artifacts/cilium-connectivity-check-1.19.2/connectivity-check-internal.0014.yaml: Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31414: provided port is already allocated
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a HCP cluster and use cilium CNI plugin1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2068856415081992192