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

Environment: STG

Failure patterns: 3 · Failures matched: 10 · 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 16: 0 · May 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 8none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:120]: Swift cluster rg-candidate-5-0-7jt2zr/cluster-candidate-5-0-898h7z should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000a159e0>: 
    failed waiting for cluster="cluster-candidate-5-0-898h7z" in resourcegroup="rg-candidate-5-0-7jt2zr" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-candidate-5-0-898h7z in resource group rg-candidate-5-0-7jt2zr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:120]: Swift cluster rg-candidate-5-0-7jt2zr/cluster-candidate-5-0-898h7z should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000a159e0>: 
    failed waiting for cluster="cluster-candidate-5-0-898h7z" in resourcegroup="rg-candidate-5-0-7jt2zr" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-candidate-5-0-898h7z in resource group rg-candidate-5-0-7jt2zr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:137]: failed to create HCP cluster "cluster-zstream-4-22-9dtk7p" with version 4.22.0-rc.2 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc00114e9f0>: 
    failed to create HCP cluster cluster-zstream-4-22-9dtk7p, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-9dtk7p in resource group rg-zstream-upgrade-4-22-68pdm8, error: failed waiting for cluster="cluster-zstream-4-22-9dtk7p" in resourcegroup="rg-zstream-upgrade-4-22-68pdm8" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-9dtk7p in resource group rg-zstream-upgrade-4-22-68pdm8, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:137]: failed to create HCP cluster "cluster-zstream-4-22-9dtk7p" with version 4.22.0-rc.2 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc00114e9f0>: 
    failed to create HCP cluster cluster-zstream-4-22-9dtk7p, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-9dtk7p in resource group rg-zstream-upgrade-4-22-68pdm8, error: failed waiting for cluster="cluster-zstream-4-22-9dtk7p" in resourcegroup="rg-zstream-upgrade-4-22-68pdm8" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-9dtk7p in resource group rg-zstream-upgrade-4-22-68pdm8, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:108]: failed to create HCP cluster "private-kv-cluster" with private keyvault
Unexpected error:
    <*fmt.wrapErrors | 0xc000c45a70>: 
    failed waiting for cluster="private-kv-cluster" in resourcegroup="private-keyvault-frs6rt" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster private-kv-cluster in resource group private-keyvault-frs6rt, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:108]: failed to create HCP cluster "private-kv-cluster" with private keyvault
Unexpected error:
    <*fmt.wrapErrors | 0xc000c45a70>: 
    failed waiting for cluster="private-kv-cluster" in resourcegroup="private-keyvault-frs6rt" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster private-kv-cluster in resource group private-keyvault-frs6rt, error: context deadline exceeded
    ...
occurred
Contributing tests (8)
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.201
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 5.01
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should create an HCP cluster and validate TLS certificates1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should not be able to reuse subnets and NSGs between clusters1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.221
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057642836106416128
failed to wait for first cluster "<cluster>" to complete creation
full failure pattern:
failed to wait for first cluster "<cluster>" to complete creation
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 16: 0 · May 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: failed to wait for first cluster "basic-hcp-cluster" to complete creation
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: failed to wait for first cluster "basic-hcp-cluster" to complete creation
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057642836106416128
validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-n12p2cds:stage-e2e-parallel" cannot get ...
full failure pattern:
validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-n12p2cds:stage-e2e-parallel" cannot get resource "validatingadmissionpolicies" in API group
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 16: 0 · May 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:135]: ValidatingAdmissionPolicy should exist
Unexpected error:
    <*errors.StatusError | 0xc000e0e140>: 
    validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-n12p2cds:stage-e2e-parallel" cannot get resource "validatingadmissionpolicies" in API group "admissionregistration.k8s.io" at the cluster scope
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:135]: ValidatingAdmissionPolicy should exist
Unexpected error:
    <*errors.StatusError | 0xc000e0e140>: 
    validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-n12p2cds:stage-e2e-parallel" cannot get resource "validatingadmissionpolicies" in API group "admissionregistration.k8s.io" at the cluster scope
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelImage Registry Policy should allow pods with images from allowed registries and have a valid allowlist1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057642836106416128