CIHealth
<
Single Day: May 26▾
Last 7 Days Weekly: May 25 - May 31 Sprint: May 25 - Jun 7 Single Day: May 26
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 4 · Failures matched: 5 · Total runs: 2 · 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)
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsMay 20: 0 · May 21: 0 · May 22: 0 · May 23: 0 · May 24: 0 · May 25: 0 · May 26: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:94]: failed to create HCP cluster for TLS endpoint test
Unexpected error:
    <*fmt.wrapErrors | 0xc001518090>: 
    failed to create HCP cluster tls-endpoint-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster tls-endpoint-hcp-cluster in resource group tls-endpoint-cluster-2vsdrb, error: failed waiting for cluster="tls-endpoint-hcp-cluster" in resourcegroup="tls-endpoint-cluster-2vsdrb" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster tls-endpoint-hcp-cluster in resource group tls-endpoint-cluster-2vsdrb, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:94]: failed to create HCP cluster for TLS endpoint test
Unexpected error:
    <*fmt.wrapErrors | 0xc001518090>: 
    failed to create HCP cluster tls-endpoint-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster tls-endpoint-hcp-cluster in resource group tls-endpoint-cluster-2vsdrb, error: failed waiting for cluster="tls-endpoint-hcp-cluster" in resourcegroup="tls-endpoint-cluster-2vsdrb" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster tls-endpoint-hcp-cluster in resource group tls-endpoint-cluster-2vsdrb, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:89]: failed to create HCP cluster "cx-rg-hcp-cluster"
Unexpected error:
    <*fmt.wrapErrors | 0xc001196090>: 
    failed to create HCP cluster cx-rg-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-mk6qtw, error: failed waiting for cluster="cx-rg-hcp-cluster" in resourcegroup="cx-rg-cluster-mk6qtw" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-mk6qtw, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:89]: failed to create HCP cluster "cx-rg-hcp-cluster"
Unexpected error:
    <*fmt.wrapErrors | 0xc001196090>: 
    failed to create HCP cluster cx-rg-hcp-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-mk6qtw, error: failed waiting for cluster="cx-rg-hcp-cluster" in resourcegroup="cx-rg-cluster-mk6qtw" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-mk6qtw, error: context deadline exceeded
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create an HCP cluster then delete it by deleting the customer resource group1
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/a2059422345214300160
tls: failed to verify certificate: x509: certificate signed by unknown authority
full failure pattern:
tls: failed to verify certificate: x509: certificate signed by unknown authority
Signal: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsMay 20: 0 · May 21: 0 · May 22: 0 · May 23: 0 · May 24: 0 · May 25: 0 · May 26: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:211]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc0000126d8>: 
    VerifySimpleWebApp failed: route was never reachable: Get "https://agnhost-e2e-serving-app-rvlq7.apps.aro.cilium-cluster.1bqw.uksouth.aroapp-hcp.azure-test.net": tls: failed to verify certificate: x509: certificate signed by unknown authority
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:211]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc0000126d8>: 
    VerifySimpleWebApp failed: route was never reachable: Get "https://agnhost-e2e-serving-app-rvlq7.apps.aro.cilium-cluster.1bqw.uksouth.aroapp-hcp.azure-test.net": tls: failed to verify certificate: x509: certificate signed by unknown authority
    ...
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/a2059422345214300160
configmaps "image-registry-allowlist-config" is forbidden: User "system:serviceaccount:ci-op-w8zrx9nj:integration-e2e-parallel" cannot get resource "configmaps" in API group "" in...
full failure pattern:
configmaps "image-registry-allowlist-config" is forbidden: User "system:serviceaccount:ci-op-w8zrx9nj:integration-e2e-parallel" cannot get resource "configmaps" in API group "" in the namespace "<namespace>"
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 20: 0 · May 21: 0 · May 22: 0 · May 23: 0 · May 24: 0 · May 25: 0 · May 26: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:144]: ConfigMap image-registry-allowlist-config should exist
Unexpected error:
    <*errors.StatusError | 0xc000d7a5a0>: 
    configmaps "image-registry-allowlist-config" is forbidden: User "system:serviceaccount:ci-op-w8zrx9nj:integration-e2e-parallel" cannot get resource "configmaps" in API group "" in the namespace "image-registry-policy"
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:144]: ConfigMap image-registry-allowlist-config should exist
Unexpected error:
    <*errors.StatusError | 0xc000d7a5a0>: 
    configmaps "image-registry-allowlist-config" is forbidden: User "system:serviceaccount:ci-op-w8zrx9nj:integration-e2e-parallel" cannot get resource "configmaps" in API group "" in the namespace "image-registry-policy"
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-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/a2059422345214300160
validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-y8clw7zc:integration-e2e-parallel" canno...
full failure pattern:
validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-y8clw7zc:integration-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
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 20: 0 · May 21: 0 · May 22: 0 · May 23: 0 · May 24: 0 · May 25: 0 · May 26: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:130]: ValidatingAdmissionPolicy should exist
Unexpected error:
    <*errors.StatusError | 0xc000db4500>: 
    validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-y8clw7zc:integration-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:130]: ValidatingAdmissionPolicy should exist
Unexpected error:
    <*errors.StatusError | 0xc000db4500>: 
    validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-y8clw7zc:integration-e2e-parallel" cannot get resource "validatingadmissionpolicies" in API group "admissionregistration.k8s.io" at the cluster scope
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-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/a2059217385671364608