CIHealth
<
Weekly: Jul 13 - Jul 19▾
Last 7 Days Weekly: Jul 13 - Jul 19 Sprint: Jul 6 - Jul 19 Single Day: Jul 19
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 7 · Failures matched: 8 · Total runs: 17 · Runs affected: 5

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.
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 3 prior week(s); active 1 day(s)
e2e211.76%2 of 17 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 2 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 0 · Jul 19: 0none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:194]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc0014903c0>: 
    VerifySimpleWebApp failed: route was never reachable: Get "https://agnhost-e2e-serving-app-bxb9f.apps.aro.cilium-cluster.h044.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:194]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc0014903c0>: 
    VerifySimpleWebApp failed: route was never reachable: Get "https://agnhost-e2e-serving-app-bxb9f.apps.aro.cilium-cluster.h044.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/complete_cluster_create_multiversion.go:172]: failed to verify simple web app runs on cluster "cluster-candidate-4-21-thmlxl"
Unexpected error:
    <*fmt.wrapError | 0xc0007e18c0>: 
    route was never reachable: Get "https://agnhost-e2e-serving-app-ftkg2.apps.aro.c7k1v4u4a1s2g0i.s1vp.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/complete_cluster_create_multiversion.go:172]: failed to verify simple web app runs on cluster "cluster-candidate-4-21-thmlxl"
Unexpected error:
    <*fmt.wrapError | 0xc0007e18c0>: 
    route was never reachable: Get "https://agnhost-e2e-serving-app-ftkg2.apps.aro.c7k1v4u4a1s2g0i.s1vp.uksouth.aroapp-hcp.azure-test.net": tls: failed to verify certificate: x509: certificate signed by unknown authority
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.211
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 (2)
Date (UTC)Associated PRProw job
n/a2077122454056079360
n/a2076886089682915328
DeleteHCPCluster timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
DeleteHCPCluster timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)
e2e15.88%1 of 17 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)Show trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 1 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:283]: Unexpected error:
    <*errors.joinError | 0xc0014583a8>: 
    failed to cleanup resource group: failed deleting hcp clusters in resourcegroup="arm64-vm-cluster-t95wmj", caused by: failed waiting for hcpCluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-t95wmj" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-t95wmj, error: context deadline exceeded, error: failed waiting for hcpCluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-t95wmj" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-t95wmj, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:283]: Unexpected error:
    <*errors.joinError | 0xc0014583a8>: 
    failed to cleanup resource group: failed deleting hcp clusters in resourcegroup="arm64-vm-cluster-t95wmj", caused by: failed waiting for hcpCluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-t95wmj" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-t95wmj, error: context deadline exceeded, error: failed waiting for hcpCluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-t95wmj" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-t95wmj, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create node pools with ARM64-based VMs1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2076956358430691328
DeleteResourceGroup timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
DeleteResourceGroup timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e15.88%1 of 17 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 1 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:145]: failed to delete customer resource group "cx-rg-cluster-g6j8kb"
Unexpected error:
    <*fmt.wrapErrors | 0xc00167a450>: 
    failed to delete resource group, caused by: timeout '60.000000' minutes exceeded during DeleteResourceGroup for resource group cx-rg-cluster-g6j8kb, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:145]: failed to delete customer resource group "cx-rg-cluster-g6j8kb"
Unexpected error:
    <*fmt.wrapErrors | 0xc00167a450>: 
    failed to delete resource group, caused by: timeout '60.000000' minutes exceeded during DeleteResourceGroup for resource group cx-rg-cluster-g6j8kb, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
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
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2076956358430691328
ERROR CODE: InternalServerError; detail message [clusterServiceNodePoolStatus] <no_message>; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: InternalServerError; detail message [clusterServiceNodePoolStatus] <no_message>; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e15.88%1 of 17 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 0 · Jul 15: 0 · Jul 16: 0 · Jul 17: 1 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:219]: failed to create no-AZ nodepool autoscale-noaz with autoscaling
Unexpected error:
    <*fmt.wrapError | 0xc000f5a0c0>: 
    failed to create NodePool autoscale-noaz: failed waiting for nodepool="autoscale-noaz" for cluster "np-autoscale-cluster" in resourcegroup="np-autoscaling-qdgskm" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/b20d6c32-9275-4bbf-aeb0-469c8eca1c01
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/b20d6c32-9275-4bbf-aeb0-469c8eca1c01",
      "name": "b20d6c32-9275-4bbf-aeb0-469c8eca1c01",
      "status": "Failed",
      "startTime": "2026-07-18T00:23:07.322814719Z",
      "endTime": "2026-07-18T00:42:14.098165935Z",
      "error": {
        "code": "InternalServerError",
        "message": "[clusterServiceNodePoolStatus] \u003cno_message\u003e"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:219]: failed to create no-AZ nodepool autoscale-noaz with autoscaling
Unexpected error:
    <*fmt.wrapError | 0xc000f5a0c0>: 
    failed to create NodePool autoscale-noaz: failed waiting for nodepool="autoscale-noaz" for cluster "np-autoscale-cluster" in resourcegroup="np-autoscaling-qdgskm" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/b20d6c32-9275-4bbf-aeb0-469c8eca1c01
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/b20d6c32-9275-4bbf-aeb0-469c8eca1c01",
      "name": "b20d6c32-9275-4bbf-aeb0-469c8eca1c01",
      "status": "Failed",
      "startTime": "2026-07-18T00:23:07.322814719Z",
      "endTime": "2026-07-18T00:42:14.098165935Z",
      "error": {
        "code": "InternalServerError",
        "message": "[clusterServiceNodePoolStatus] \u003cno_message\u003e"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled up to replica limits1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2078254388849152000
VerifyHostedControlPlaneZStreamUpgradeOnly(initial=4
full failure pattern:
VerifyHostedControlPlaneZStreamUpgradeOnly(initial=4
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e15.88%1 of 17 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 1 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:131]: Timed out after 2700.004s.
Expected success, but got an error:
    <*errors.joinError | 0xc00172dc08>: 
    VerifyHostedControlPlaneZStreamUpgradeOnly(initial=4.20.28) failed: no version in clusterversion/version status.history is greater than initial "4.20.28"
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:131]: Timed out after 2700.004s.
Expected success, but got an error:
    <*errors.joinError | 0xc00172dc08>: 
    VerifyHostedControlPlaneZStreamUpgradeOnly(initial=4.20.28) failed: no version in clusterversion/version status.history is greater than initial "4.20.28"
    ...
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.201
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2076956358430691328
failed to create console OAuth client secret for external auth <external-auth> VM
full failure pattern:
failed to create console OAuth client secret for external auth <external-auth> VM
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e15.88%1 of 17 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 0 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 1 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:396]: failed to create console OAuth client secret for external auth via VM
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:396]: failed to create console OAuth client secret for external auth via VM
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2078579174016028672
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)
e2e15.88%1 of 17 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 1 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:289]: failed to create HCP cluster node-limit-cluster with MaxNodesTotal limit
Unexpected error:
    <*fmt.wrapErrors | 0xc000978b40>: 
    failed to create HCP cluster node-limit-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster node-limit-cluster in resource group node-limit-test-vmtz78, error: failed waiting for cluster="node-limit-cluster" in resourcegroup="node-limit-test-vmtz78" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster node-limit-cluster in resource group node-limit-test-vmtz78, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:289]: failed to create HCP cluster node-limit-cluster with MaxNodesTotal limit
Unexpected error:
    <*fmt.wrapErrors | 0xc000978b40>: 
    failed to create HCP cluster node-limit-cluster, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster node-limit-cluster in resource group node-limit-test-vmtz78, error: failed waiting for cluster="node-limit-cluster" in resourcegroup="node-limit-test-vmtz78" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster node-limit-cluster in resource group node-limit-test-vmtz78, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should respect cluster-wide node limits with nodepool autoscaling1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2076886089682915328