CIHealth
<
Single Day: Jul 24▾
Last 7 Days Weekly: Jul 20 - Jul 26 Sprint: Jul 20 - Aug 2 Single Day: Jul 24
Custom time window
> Reset
View JSON API

Environment: STG

Failure patterns: 3 · Failures matched: 3 · Total runs: 4 · 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.
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 2 day(s)
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 2 day(s)Show trend detailsJul 18: 0 · Jul 19: 1 · Jul 20: 0 · Jul 21: 0 · Jul 22: 0 · Jul 23: 0 · Jul 24: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:186]: failed to verify simple web app runs on cluster "cluster-candidate-4-22-9p9q96"
Unexpected error:
    <*fmt.wrapError | 0xc000e3e200>: 
    [strict TLS verification] route was never reachable: Get "https://agnhost-e2e-sample-app-5s5tl.apps.aro.t4h5n3m8h9b6b1y.pmy9.uksouthstaging.aroapp-hcp.io": 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:186]: failed to verify simple web app runs on cluster "cluster-candidate-4-22-9p9q96"
Unexpected error:
    <*fmt.wrapError | 0xc000e3e200>: 
    [strict TLS verification] route was never reachable: Get "https://agnhost-e2e-sample-app-5s5tl.apps.aro.t4h5n3m8h9b6b1y.pmy9.uksouthstaging.aroapp-hcp.io": tls: failed to verify certificate: x509: certificate signed by unknown authority
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.221
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2080621562049859584
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 — seen in 1 prior week(s); active 3 day(s)
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 3 day(s)Show trend detailsJul 18: 1 · Jul 19: 0 · Jul 20: 2 · Jul 21: 0 · Jul 22: 0 · Jul 23: 0 · Jul 24: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:138]: failed to create node pools in parallel for cluster "cx-rg-hcp-cluster"
Unexpected error:
    <*fmt.wrapError | 0xc0004ef8c0>: 
    failed to create NodePool np-2: failed waiting for nodepool="np-2" for cluster "cx-rg-hcp-cluster" in resourcegroup="cx-rg-cluster-7pjp2fntgwhc" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/c569a933-5592-4cb9-951a-4e439ed8e930
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/c569a933-5592-4cb9-951a-4e439ed8e930",
      "name": "c569a933-5592-4cb9-951a-4e439ed8e930",
      "status": "Failed",
      "startTime": "2026-07-24T02:16:26.672204644Z",
      "endTime": "2026-07-24T02:35:27.643263493Z",
      "error": {
        "code": "InternalServerError",
        "message": "[clusterServiceNodePoolStatus] \u003cno_message\u003e"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:138]: failed to create node pools in parallel for cluster "cx-rg-hcp-cluster"
Unexpected error:
    <*fmt.wrapError | 0xc0004ef8c0>: 
    failed to create NodePool np-2: failed waiting for nodepool="np-2" for cluster "cx-rg-hcp-cluster" in resourcegroup="cx-rg-cluster-7pjp2fntgwhc" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/c569a933-5592-4cb9-951a-4e439ed8e930
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/c569a933-5592-4cb9-951a-4e439ed8e930",
      "name": "c569a933-5592-4cb9-951a-4e439ed8e930",
      "status": "Failed",
      "startTime": "2026-07-24T02:16:26.672204644Z",
      "endTime": "2026-07-24T02:35:27.643263493Z",
      "error": {
        "code": "InternalServerError",
        "message": "[clusterServiceNodePoolStatus] \u003cno_message\u003e"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-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/a2080473235987632128
failed to create cluster role binding for external auth <external-auth> VM
full failure pattern:
failed to create cluster role binding for external auth <external-auth> VM
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 18: 0 · Jul 19: 0 · Jul 20: 0 · Jul 21: 0 · Jul 22: 0 · Jul 23: 0 · Jul 24: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:328]: failed to create cluster role binding 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:328]: failed to create cluster role binding for external auth via VM
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2080473235987632128