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

Environment: INT

Failure patterns: 5 · Failures matched: 20 · Total runs: 29 · Runs affected: 13

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 5 days
e2e1137.93%11 of 29 job runs affectedFlakeSignal: Flake — present in 4 prior week(s); spread across 5 daysShow trend detailsJun 21: 0 · Jun 22: 2 · Jun 23: 2 · Jun 24: 6 · Jun 25: 4 · Jun 26: 2 · Jun 27: 0 · Jun 28: 0none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:104]: failed to create HCP cluster "cilium-cluster" with no CNI and private etcd
Unexpected error:
    <*fmt.wrapErrors | 0xc000764120>: 
    failed waiting for cluster="cilium-cluster" in resourcegroup="complex-cilium-kv-rb9trs" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cilium-cluster in resource group complex-cilium-kv-rb9trs, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:104]: failed to create HCP cluster "cilium-cluster" with no CNI and private etcd
Unexpected error:
    <*fmt.wrapErrors | 0xc000764120>: 
    failed waiting for cluster="cilium-cluster" in resourcegroup="complex-cilium-kv-rb9trs" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cilium-cluster in resource group complex-cilium-kv-rb9trs, 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-sv8tjk" with version 4.22.1 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc000e4c060>: 
    failed to create HCP cluster cluster-zstream-4-22-sv8tjk, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-sv8tjk in resource group rg-zstream-upgrade-4-22-l997c2, error: failed waiting for cluster="cluster-zstream-4-22-sv8tjk" in resourcegroup="rg-zstream-upgrade-4-22-l997c2" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-sv8tjk in resource group rg-zstream-upgrade-4-22-l997c2, 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-sv8tjk" with version 4.22.1 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc000e4c060>: 
    failed to create HCP cluster cluster-zstream-4-22-sv8tjk, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-sv8tjk in resource group rg-zstream-upgrade-4-22-l997c2, error: failed waiting for cluster="cluster-zstream-4-22-sv8tjk" in resourcegroup="rg-zstream-upgrade-4-22-l997c2" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-sv8tjk in resource group rg-zstream-upgrade-4-22-l997c2, 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-dr5mvl" with version 4.22.0 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc00098a870>: 
    failed to create HCP cluster cluster-zstream-4-22-dr5mvl, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-dr5mvl in resource group rg-zstream-upgrade-4-22-bfspcz, error: failed waiting for cluster="cluster-zstream-4-22-dr5mvl" in resourcegroup="rg-zstream-upgrade-4-22-bfspcz" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-dr5mvl in resource group rg-zstream-upgrade-4-22-bfspcz, 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-dr5mvl" with version 4.22.0 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc00098a870>: 
    failed to create HCP cluster cluster-zstream-4-22-dr5mvl, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-dr5mvl in resource group rg-zstream-upgrade-4-22-bfspcz, error: failed waiting for cluster="cluster-zstream-4-22-dr5mvl" in resourcegroup="rg-zstream-upgrade-4-22-bfspcz" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-dr5mvl in resource group rg-zstream-upgrade-4-22-bfspcz, error: context deadline exceeded
    ...
occurred
Contributing tests (7)
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.228
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelUpdate HCPOpenShiftCluster Negative creates a cluster and fails to update its name with a PATCH request2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-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-integration-e2e-parallelCustomer should be able to create an HCP cluster and manage pull secrets1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster with back-level version 4.191
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should not be able to reuse subnets and NSGs between clusters1
Affected runs (11)
Date (UTC)Associated PRProw job
n/a2070615009901154304
n/a2070361227929849856
n/a2070277880654336000
n/a2070231729485910016
n/a2069899032448208896
n/a2069631727260667904
n/a2069573511558467584
n/a2069514197628096512
n/a2069240121583996928
n/a2068956060353302528
n/a2068856415081992192
x509: certificate signed by unknown authority
full failure pattern:
x509: certificate signed by unknown authority
Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)
e2e13.45%1 of 29 job runs affectedIndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)Show trend detailsJun 21: 1 · Jun 22: 0 · Jun 23: 0 · Jun 24: 0 · Jun 25: 0 · Jun 26: 1 · Jun 27: 0 · Jun 28: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:167]: Timed out after 600.132s.
expect ingress certificate to be signed by a trusted Azure CA
Expected success, but got an error:
    <x509.UnknownAuthorityError>: 
    x509: certificate signed by unknown authority
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:167]: Timed out after 600.132s.
expect ingress certificate to be signed by a trusted Azure CA
Expected success, but got an error:
    <x509.UnknownAuthorityError>: 
    x509: certificate signed by unknown authority
    ...
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should create an HCP cluster and validate TLS certificates1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2070533078811414528
Cluster should become ready within '20.000000' minutes
full failure pattern:
Cluster should become ready within '20.000000' minutes
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)
e2e13.45%1 of 29 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)Show trend detailsJun 21: 0 · Jun 22: 0 · Jun 23: 0 · Jun 24: 1 · Jun 25: 0 · Jun 26: 0 · Jun 27: 0 · Jun 28: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:162]: Timed out after 1200.001s.
Cluster should become ready within '20.000000' minutes
Expected
    <bool>: ...
to be true
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:162]: Timed out after 1200.001s.
Cluster should become ready within '20.000000' minutes
Expected
    <bool>: ...
to be true
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-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/a2069573511558467584
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)
e2e13.45%1 of 29 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsJun 21: 0 · Jun 22: 0 · Jun 23: 0 · Jun 24: 0 · Jun 25: 0 · Jun 26: 1 · Jun 27: 0 · Jun 28: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:190]: failed to verify nodes are Ready with Cilium CNI for cluster "cilium-cluster"
Unexpected error:
    <*errors.joinError | 0xc001c7ad50>: 
    failed to create NodePool cilium-np, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool cilium-np in resource group complex-cilium-kv-l9xh4z, error: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-l9xh4z" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:190]: failed to verify nodes are Ready with Cilium CNI for cluster "cilium-cluster"
Unexpected error:
    <*errors.joinError | 0xc001c7ad50>: 
    failed to create NodePool cilium-np, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool cilium-np in resource group complex-cilium-kv-l9xh4z, error: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-l9xh4z" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2070312313818189824
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
e2e13.45%1 of 29 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 21: 0 · Jun 22: 1 · Jun 23: 0 · Jun 24: 0 · Jun 25: 0 · Jun 26: 0 · Jun 27: 0 · Jun 28: 0none
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