CIHealth
<
Single Day: Apr 11▾
Last 7 Days Weekly: Apr 6 - Apr 12 Sprint: Mar 30 - Apr 12 Single Day: Apr 11
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 3 · Failures matched: 4 · Total runs: 5 · 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 GetAdminRESTConfigForHCPCluster while waiting for hcpcluster creds
full failure pattern:
timeout during GetAdminRESTConfigForHCPCluster while waiting for hcpcluster creds
Signal: IndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)
e2e120.00%1 of 5 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsApr 5: 0 · Apr 6: 0 · Apr 7: 0 · Apr 8: 0 · Apr 9: 0 · Apr 10: 0 · Apr 11: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:126]: Unexpected error:
    <*fmt.wrapErrors | 0xc000fb8240>: 
    failed waiting for hcpCluster="cilium-cluster" in resourcegroup="e2e-cilium-k8c4qd" to finish getting creds, caused by: timeout '10.000000' minutes exceeded during GetAdminRESTConfigForHCPCluster for cluster cilium-cluster in resource group e2e-cilium-k8c4qd, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:126]: Unexpected error:
    <*fmt.wrapErrors | 0xc000fb8240>: 
    failed waiting for hcpCluster="cilium-cluster" in resourcegroup="e2e-cilium-k8c4qd" to finish getting creds, caused by: timeout '10.000000' minutes exceeded during GetAdminRESTConfigForHCPCluster for cluster cilium-cluster in resource group e2e-cilium-k8c4qd, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_update.go:94]: Unexpected error:
    <*fmt.wrapErrors | 0xc000efb1a0>: 
    failed waiting for hcpCluster="patch-name-cluster" in resourcegroup="patch-name-h9v6fn" to finish getting creds, caused by: timeout '10.000000' minutes exceeded during GetAdminRESTConfigForHCPCluster for cluster patch-name-cluster in resource group patch-name-h9v6fn, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_update.go:94]: Unexpected error:
    <*fmt.wrapErrors | 0xc000efb1a0>: 
    failed waiting for hcpCluster="patch-name-cluster" in resourcegroup="patch-name-h9v6fn" to finish getting creds, caused by: timeout '10.000000' minutes exceeded during GetAdminRESTConfigForHCPCluster for cluster patch-name-cluster in resource group patch-name-h9v6fn, error: context deadline exceeded
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-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
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelUpdate HCPOpenShiftCluster Negative creates a cluster and fails to update its name with a PATCH request1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2042819358987653120
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)
e2e120.00%1 of 5 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsApr 5: 0 · Apr 6: 0 · Apr 7: 0 · Apr 8: 0 · Apr 9: 0 · Apr 10: 0 · Apr 11: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:108]: Unexpected error:
    <*fmt.wrapErrors | 0xc000a42600>: 
    failed waiting for cluster="private-kv-cluster" in resourcegroup="private-keyvault-7x2n96" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster private-kv-cluster in resource group private-keyvault-7x2n96, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:108]: Unexpected error:
    <*fmt.wrapErrors | 0xc000a42600>: 
    failed waiting for cluster="private-kv-cluster" in resourcegroup="private-keyvault-7x2n96" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster private-kv-cluster in resource group private-keyvault-7x2n96, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2042908344267575296
tls: failed to verify certificate: x509: certificate is valid for <hcp-api-host>, <hcp-api-host>, not <hcp-api-host>
full failure pattern:
tls: failed to verify certificate: x509: certificate is valid for <hcp-api-host>, <hcp-api-host>, not <hcp-api-host>
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e120.00%1 of 5 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsApr 5: 0 · Apr 6: 0 · Apr 7: 0 · Apr 8: 0 · Apr 9: 0 · Apr 10: 0 · Apr 11: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/oidc_issuer_workload_identity.go:243]: Unexpected error:
    <*errors.joinError | 0xc00137f3f8>: 
    VerifyBasicAccess failed: failed to list services: Get "https://api.oidc-wi-cluster.w4ht.uksouth.aroapp-hcp.azure-test.net:443/api/v1/namespaces/default/services": tls: failed to verify certificate: x509: certificate is valid for api.oidc-wi-cluster.foaj.uksouth.aroapp-hcp.azure-test.net, reserved.aroapp-hcp.azure-test.net, not api.oidc-wi-cluster.w4ht.uksouth.aroapp-hcp.azure-test.net
    VerifyAllAPIServicesAvailable failed: failed to list all APIServices: Get "https://api.oidc-wi-cluster.w4ht.uksouth.aroapp-hcp.azure-test.net:443/apis/apiregistration.k8s.io/v1/apiservices": tls: failed to verify certificate: x509: certificate is valid for api.oidc-wi-cluster.foaj.uksouth.aroapp-hcp.azure-test.net, reserved.aroapp-hcp.azure-test.net, not api.oidc-wi-cluster.w4ht.uksouth.aroapp-hcp.azure-test.net
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/oidc_issuer_workload_identity.go:243]: Unexpected error:
    <*errors.joinError | 0xc00137f3f8>: 
    VerifyBasicAccess failed: failed to list services: Get "https://api.oidc-wi-cluster.w4ht.uksouth.aroapp-hcp.azure-test.net:443/api/v1/namespaces/default/services": tls: failed to verify certificate: x509: certificate is valid for api.oidc-wi-cluster.foaj.uksouth.aroapp-hcp.azure-test.net, reserved.aroapp-hcp.azure-test.net, not api.oidc-wi-cluster.w4ht.uksouth.aroapp-hcp.azure-test.net
    VerifyAllAPIServicesAvailable failed: failed to list all APIServices: Get "https://api.oidc-wi-cluster.w4ht.uksouth.aroapp-hcp.azure-test.net:443/apis/apiregistration.k8s.io/v1/apiservices": tls: failed to verify certificate: x509: certificate is valid for api.oidc-wi-cluster.foaj.uksouth.aroapp-hcp.azure-test.net, reserved.aroapp-hcp.azure-test.net, not api.oidc-wi-cluster.w4ht.uksouth.aroapp-hcp.azure-test.net
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to use workload identity via the cluster OIDC issuer URL1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2042819358987653120