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

Environment: INT

Failure patterns: 3 · Failures matched: 3 · Total runs: 8 · Runs affected: 3

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: InvalidRequestContent; detail message Cluster '<id>' is in state 'pending_update', can't update; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: InvalidRequestContent; detail message Cluster '<id>' is in state 'pending_update', can't update; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 2 day(s)
e2e112.50%1 of 8 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 2 day(s)Show trend detailsApr 9: 1 · Apr 10: 0 · Apr 11: 0 · Apr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/idms_lifecycle.go:178]: Unexpected error:
    <*exported.ResponseError | 0xc0011b52f0>: 
    PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/idms-wr2r48/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/idms-e2e-hcp-cluster
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2pmeojr923nt08rchn2mn56al24muh61' is in state 'pending_update', can't update"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/idms_lifecycle.go:178]: Unexpected error:
    <*exported.ResponseError | 0xc0011b52f0>: 
    PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/idms-wr2r48/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/idms-e2e-hcp-cluster
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2pmeojr923nt08rchn2mn56al24muh61' is in state 'pending_update', can't update"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster and manage ImageDigestMirrors1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2044298200289906688
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)
e2e112.50%1 of 8 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsApr 9: 0 · Apr 10: 0 · Apr 11: 0 · Apr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:147]: Unexpected error:
    <*fmt.wrapErrors | 0xc000272fc0>: 
    failed to create NodePool npupgrade-4-20, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool npupgrade-4-20 in resource group rg-np-version-upgrade-bxk5sm-8jb9jj, error: failed waiting for nodepool="npupgrade-4-20" for cluster "np-version-upgrade-cluster-bxk5sm" in resourcegroup="rg-np-version-upgrade-bxk5sm-8jb9jj" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:147]: Unexpected error:
    <*fmt.wrapErrors | 0xc000272fc0>: 
    failed to create NodePool npupgrade-4-20, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool npupgrade-4-20 in resource group rg-np-version-upgrade-bxk5sm-8jb9jj, error: failed waiting for nodepool="npupgrade-4-20" for cluster "np-version-upgrade-cluster-bxk5sm" in resourcegroup="rg-np-version-upgrade-bxk5sm-8jb9jj" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.20.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2044254736290418688
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)
e2e112.50%1 of 8 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsApr 9: 0 · Apr 10: 0 · Apr 11: 0 · Apr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:99]: Unexpected error:
    <*fmt.wrapErrors | 0xc000a2c840>: 
    failed waiting for hcpCluster="cx-rg-hcp-cluster" in resourcegroup="cx-rg-cluster-9wb52w" to finish getting creds, caused by: timeout '10.000000' minutes exceeded during GetAdminRESTConfigForHCPCluster for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-9wb52w, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:99]: Unexpected error:
    <*fmt.wrapErrors | 0xc000a2c840>: 
    failed waiting for hcpCluster="cx-rg-hcp-cluster" in resourcegroup="cx-rg-cluster-9wb52w" to finish getting creds, caused by: timeout '10.000000' minutes exceeded during GetAdminRESTConfigForHCPCluster for cluster cx-rg-hcp-cluster in resource group cx-rg-cluster-9wb52w, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-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/a2044459688325550080