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

Environment: PROD

Failure patterns: 2 · Failures matched: 2 · Total runs: 2 · Runs affected: 1

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; context ; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: InternalServerError; context ; provider Microsoft.RedHatOpenShift
Signal: FlakeSignal: Flake — present in 2 prior week(s); spread across 3 days
e2e150.00%1 of 2 job runs affectedFlakeSignal: Flake — present in 2 prior week(s); spread across 3 daysShow trend detailsApr 10: 8 · Apr 11: 0 · Apr 12: 4 · Apr 13: 0 · Apr 14: 0 · Apr 15: 0 · Apr 16: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:276]: Unexpected error:
    <*fmt.wrapError | 0xc000d80d00>: 
    failed to create HCP cluster node-limit-cluster: failed waiting for cluster="node-limit-cluster" in resourcegroup="node-limit-test-wxq5cb" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/37230de7-e1d1-4a57-b4b5-81ff612cb3c2
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/37230de7-e1d1-4a57-b4b5-81ff612cb3c2",
      "name": "37230de7-e1d1-4a57-b4b5-81ff612cb3c2",
      "status": "Failed",
      "startTime": "2026-04-16T02:48:07.958082161Z",
      "endTime": "2026-04-16T02:49:14.016455598Z",
      "error": {
        "code": "InternalServerError"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:276]: Unexpected error:
    <*fmt.wrapError | 0xc000d80d00>: 
    failed to create HCP cluster node-limit-cluster: failed waiting for cluster="node-limit-cluster" in resourcegroup="node-limit-test-wxq5cb" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/37230de7-e1d1-4a57-b4b5-81ff612cb3c2
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/37230de7-e1d1-4a57-b4b5-81ff612cb3c2",
      "name": "37230de7-e1d1-4a57-b4b5-81ff612cb3c2",
      "status": "Failed",
      "startTime": "2026-04-16T02:48:07.958082161Z",
      "endTime": "2026-04-16T02:49:14.016455598Z",
      "error": {
        "code": "InternalServerError"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should respect cluster-wide node limits with nodepool autoscaling1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2044596653750489088
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)
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsApr 10: 0 · Apr 11: 0 · Apr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 0 · Apr 16: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:118]: Unexpected error:
    <*fmt.wrapErrors | 0xc0021c10b0>: 
    failed waiting for hcpCluster="np-autoscale-cluster" in resourcegroup="np-autoscaling-phhpch" to finish getting creds, caused by: timeout '10.000000' minutes exceeded during GetAdminRESTConfigForHCPCluster for cluster np-autoscale-cluster in resource group np-autoscaling-phhpch, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:118]: Unexpected error:
    <*fmt.wrapErrors | 0xc0021c10b0>: 
    failed waiting for hcpCluster="np-autoscale-cluster" in resourcegroup="np-autoscaling-phhpch" to finish getting creds, caused by: timeout '10.000000' minutes exceeded during GetAdminRESTConfigForHCPCluster for cluster np-autoscale-cluster in resource group np-autoscaling-phhpch, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-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/a2044596653750489088