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

Environment: INT

Failure patterns: 4 · Failures matched: 10 · Total runs: 5 · Runs affected: 4

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.
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: FlakeSignal: Flake — present in 2 prior week(s); spread across 3 days
e2e120.00%1 of 5 job runs affectedFlakeSignal: Flake — present in 2 prior week(s); spread across 3 daysShow trend detailsJul 24: 0 · Jul 25: 0 · Jul 26: 0 · Jul 27: 1 · Jul 28: 0 · Jul 29: 1 · Jul 30: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:131]: failed to create GPU nodepool gpu-np-1 with VM size Standard_NC4as_T4_v3
Unexpected error:
    <*fmt.wrapError | 0xc000f22760>: 
    failed to create NodePool gpu-np-1: failed waiting for nodepool="gpu-np-1" for cluster "cluster-gpu-np" in resourcegroup="rg-gpu-nodepool-nv2l5l98hkzq" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/d7b8561b-0d3d-47ac-a57b-83cd6af7d375
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/d7b8561b-0d3d-47ac-a57b-83cd6af7d375",
      "name": "d7b8561b-0d3d-47ac-a57b-83cd6af7d375",
      "status": "Failed",
      "startTime": "2026-07-30T07:33:49.233891501Z",
      "endTime": "2026-07-30T07:53:06.946835167Z",
      "error": {
        "code": "InternalServerError",
        "message": "[clusterServiceNodePoolStatus] \u003cno_message\u003e"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:131]: failed to create GPU nodepool gpu-np-1 with VM size Standard_NC4as_T4_v3
Unexpected error:
    <*fmt.wrapError | 0xc000f22760>: 
    failed to create NodePool gpu-np-1: failed waiting for nodepool="gpu-np-1" for cluster "cluster-gpu-np" in resourcegroup="rg-gpu-nodepool-nv2l5l98hkzq" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/d7b8561b-0d3d-47ac-a57b-83cd6af7d375
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/d7b8561b-0d3d-47ac-a57b-83cd6af7d375",
      "name": "d7b8561b-0d3d-47ac-a57b-83cd6af7d375",
      "status": "Failed",
      "startTime": "2026-07-30T07:33:49.233891501Z",
      "endTime": "2026-07-30T07:53:06.946835167Z",
      "error": {
        "code": "InternalServerError",
        "message": "[clusterServiceNodePoolStatus] \u003cno_message\u003e"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelHCP Nodepools GPU instances creates and deletes a GPU nodepool in a single cluster1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2082716084711985152
failed to create service principal: create service principal: error status code received from the API
full failure pattern:
failed to create service principal: create service principal: error status code received from the API
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e480.00%4 of 5 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 24: 0 · Jul 25: 0 · Jul 26: 0 · Jul 27: 0 · Jul 28: 0 · Jul 29: 0 · Jul 30: 7none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:264]: failed to create app registration with service principal
Unexpected error:
    <*fmt.wrapError | 0xc000f05de0>: 
    failed to create service principal: create service principal: error status code received from the API
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:264]: failed to create app registration with service principal
Unexpected error:
    <*fmt.wrapError | 0xc000f05de0>: 
    failed to create service principal: create service principal: error status code received from the API
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_create.go:127]: failed to create app registration with service principal
Unexpected error:
    <*fmt.wrapError | 0xc00150b9e0>: 
    failed to create service principal: create service principal: error status code received from the API
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_create.go:127]: failed to create app registration with service principal
Unexpected error:
    <*fmt.wrapError | 0xc00150b9e0>: 
    failed to create service principal: create service principal: error status code received from the API
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:264]: failed to create app registration with service principal
Unexpected error:
    <*fmt.wrapError | 0xc0002199a0>: 
    failed to create service principal: create service principal: error status code received from the API
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:264]: failed to create app registration with service principal
Unexpected error:
    <*fmt.wrapError | 0xc0002199a0>: 
    failed to create service principal: create service principal: error status code received from the API
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP4
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a cluster with an external auth config and get the external auth config3
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2082864512502861824
n/a2082786541406523392
n/a2082716084711985152
n/a2082652897543196672
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 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 detailsJul 24: 0 · Jul 25: 0 · Jul 26: 0 · Jul 27: 0 · Jul 28: 0 · Jul 29: 0 · Jul 30: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:289]: Unexpected error:
    <*errors.joinError | 0xc000e98318>: 
    failed to cleanup resource group: failed deleting hcp clusters in resourcegroup="patch-tags-4tr4cgtrvmhr", caused by: failed waiting for hcpCluster="patch-tags-cluster" in resourcegroup="patch-tags-4tr4cgtrvmhr" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster patch-tags-cluster in resource group patch-tags-4tr4cgtrvmhr, error: context deadline exceeded, error: failed waiting for hcpCluster="patch-tags-cluster" in resourcegroup="patch-tags-4tr4cgtrvmhr" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster patch-tags-cluster in resource group patch-tags-4tr4cgtrvmhr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:289]: Unexpected error:
    <*errors.joinError | 0xc000e98318>: 
    failed to cleanup resource group: failed deleting hcp clusters in resourcegroup="patch-tags-4tr4cgtrvmhr", caused by: failed waiting for hcpCluster="patch-tags-cluster" in resourcegroup="patch-tags-4tr4cgtrvmhr" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster patch-tags-cluster in resource group patch-tags-4tr4cgtrvmhr, error: context deadline exceeded, error: failed waiting for hcpCluster="patch-tags-cluster" in resourcegroup="patch-tags-4tr4cgtrvmhr" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster patch-tags-cluster in resource group patch-tags-4tr4cgtrvmhr, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelUpdate HCPOpenShiftCluster Positive creates a cluster and updates tags with a PATCH request1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2082864512502861824
expected <count> ready (and schedulable) nodes, found <count>
full failure pattern:
expected <count> ready (and schedulable) nodes, found <count>
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 detailsJul 24: 0 · Jul 25: 0 · Jul 26: 0 · Jul 27: 0 · Jul 28: 0 · Jul 29: 0 · Jul 30: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:232]: failed to verify 3 ready and schedulable nodes for nodepool npupgrade-4-21 after upgrade
Expected success, but got an error:
    <*errors.errorString | 0xc002b03f00>: 
    expected 3 ready (and schedulable) nodes in node pool "npupgrade-4-21", found 4
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:232]: failed to verify 3 ready and schedulable nodes for nodepool npupgrade-4-21 after upgrade
Expected success, but got an error:
    <*errors.errorString | 0xc002b03f00>: 
    expected 3 ready (and schedulable) nodes in node pool "npupgrade-4-21", found 4
    ...
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should upgrade and update a nodepool from 4.21.z to 4.21.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2082716084711985152