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

Environment: PROD

Failure patterns: 8 · Failures matched: 27 · Total runs: 30 · Runs affected: 13

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.
timeout during CreateHCPClusterAndWait; context deadline exceeded
full failure pattern:
timeout during CreateHCPClusterAndWait; context deadline exceeded
Signal: FlakeSignal: Flake — present in 4 prior week(s); spread across 4 days
e2e413.33%4 of 30 job runs affectedFlakeSignal: Flake — present in 4 prior week(s); spread across 4 daysShow trend detailsApr 12: 0 · Apr 13: 1 · Apr 14: 11 · Apr 15: 0 · Apr 16: 0 · Apr 17: 1 · Apr 18: 1 · Apr 19: 0none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:141]: Unexpected error:
    <*fmt.wrapErrors | 0xc000879980>: 
    failed to create HCP cluster cluster-zstream-4-20-6bvzql, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-20-6bvzql in resource group rg-zstream-upgrade-4-20-6lsq82, error: failed waiting for cluster="cluster-zstream-4-20-6bvzql" in resourcegroup="rg-zstream-upgrade-4-20-6lsq82" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-20-6bvzql in resource group rg-zstream-upgrade-4-20-6lsq82, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:141]: Unexpected error:
    <*fmt.wrapErrors | 0xc000879980>: 
    failed to create HCP cluster cluster-zstream-4-20-6bvzql, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-20-6bvzql in resource group rg-zstream-upgrade-4-20-6lsq82, error: failed waiting for cluster="cluster-zstream-4-20-6bvzql" in resourcegroup="rg-zstream-upgrade-4-20-6lsq82" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-20-6bvzql in resource group rg-zstream-upgrade-4-20-6lsq82, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:104]: Unexpected error:
    <*fmt.wrapErrors | 0xc00123a570>: 
    failed waiting for cluster="cilium-cluster" in resourcegroup="complex-cilium-kv-xhrrcv" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cilium-cluster in resource group complex-cilium-kv-xhrrcv, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:104]: Unexpected error:
    <*fmt.wrapErrors | 0xc00123a570>: 
    failed waiting for cluster="cilium-cluster" in resourcegroup="complex-cilium-kv-xhrrcv" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cilium-cluster in resource group complex-cilium-kv-xhrrcv, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/arm64_nodepool.go:90]: Unexpected error:
    <*fmt.wrapErrors | 0xc0014fcde0>: 
    failed to create HCP cluster arm64-vm-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-bc85j4, error: failed waiting for cluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-bc85j4" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-bc85j4, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/arm64_nodepool.go:90]: Unexpected error:
    <*fmt.wrapErrors | 0xc0014fcde0>: 
    failed to create HCP cluster arm64-vm-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-bc85j4, error: failed waiting for cluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-bc85j4" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-bc85j4, error: context deadline exceeded
    ...
occurred
Contributing tests (14)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to create an HCP cluster with Image Registry not present1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to create node pools with ARM64-based VMs1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to forward control plane logs to a storage account via shoebox diagnostic settings1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to update node pool labels and taints1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to update nodepool replicas and autoscaling1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to use workload identity via the cluster OIDC issuer URL1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should not be able to perform various invalid operations on cluster resources1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.20.zLatest1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelNodepool Ephemeral OS Disk should create a nodepool with ephemeral OS disk when autoRepair is enabled1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.191
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.201
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelUpdate HCPOpenShiftCluster Negative creates a cluster and fails to update its name with a PATCH request1
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2045321424989589504
n/a2044959032334094336
n/a2043896250377441280
n/a2043491266175438848
expected 4 nodes, found 5
full failure pattern:
expected 4 nodes, found 5
Signal: IndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior history
e2e413.33%4 of 30 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior historyShow trend detailsApr 12: 0 · Apr 13: 0 · Apr 14: 2 · Apr 15: 2 · Apr 16: 0 · Apr 17: 0 · Apr 18: 0 · Apr 19: 0none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc000ddc1c0>: 
    expected 4 nodes, found 5
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc000ddc1c0>: 
    expected 4 nodes, found 5
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc000ff0ef0>: 
    expected 4 nodes, found 5
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc000ff0ef0>: 
    expected 4 nodes, found 5
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc0006b7ab0>: 
    expected 4 nodes, found 5
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc0006b7ab0>: 
    expected 4 nodes, found 5
    ...
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to update nodepool replicas and autoscaling4
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2044421226465595392
n/a2044346239444586496
n/a2044063738033606656
n/a2043992098012663808
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 2 prior week(s); active 2 day(s)
e2e310.00%3 of 30 job runs affectedIndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)Show trend detailsApr 12: 0 · Apr 13: 0 · Apr 14: 2 · Apr 15: 1 · Apr 16: 0 · Apr 17: 0 · Apr 18: 0 · Apr 19: 0none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc000cb0660>: 
    failed to create NodePool np-1, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-dwmdj6, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-dwmdj6" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc000cb0660>: 
    failed to create NodePool np-1, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-dwmdj6, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-dwmdj6" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc001012960>: 
    failed to create NodePool np-1, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-965gz6, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-965gz6" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc001012960>: 
    failed to create NodePool np-1, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-965gz6, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-965gz6" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc000e00090>: 
    failed to create NodePool np-1, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-8qlspn, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-8qlspn" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc000e00090>: 
    failed to create NodePool np-1, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-8qlspn, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-8qlspn" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API3
Affected runs (3)
Date (UTC)Associated PRProw job
n/a2044295773960540160
n/a2043992098012663808
n/a2043959110528929792
failed waiting for nodepool="<nodepool>" for cluster "<cluster>" in resourcegroup="<resource-group>" to finish creating: context deadline exceeded
full failure pattern:
failed waiting for nodepool="<nodepool>" for cluster "<cluster>" in resourcegroup="<resource-group>" to finish creating: context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)
e2e26.67%2 of 30 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)Show trend detailsApr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 2 · Apr 16: 0 · Apr 17: 0 · Apr 18: 0 · Apr 19: 0none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc00132a1a0>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-7jmwwn" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc00132a1a0>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-7jmwwn" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc000118040>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-hcd2ng" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc000118040>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-hcd2ng" to finish creating: 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 no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully2
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2044419001106305024
n/a2044346239444586496
ERROR CODE: InternalServerError; context ; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: InternalServerError; context ; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)
e2e13.33%1 of 30 job runs affectedIndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)Show trend detailsApr 12: 4 · Apr 13: 0 · Apr 14: 0 · Apr 15: 0 · Apr 16: 1 · Apr 17: 0 · Apr 18: 0 · Apr 19: 0none
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
tls: failed to verify certificate: x509: certificate is valid for <hcp-api-host>, <hcp-api-host>, not <hcp-api-host>
full failure pattern:
tls: failed to verify certificate: x509: certificate is valid for <hcp-api-host>, <hcp-api-host>, not <hcp-api-host>
Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)
e2e13.33%1 of 30 job runs affectedIndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)Show trend detailsApr 12: 1 · Apr 13: 0 · Apr 14: 0 · Apr 15: 1 · Apr 16: 0 · Apr 17: 0 · Apr 18: 0 · Apr 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:161]: Unexpected error:
    <*url.Error | 0xc00161c840>: 
    Get "https://api.a5t3f6u4j8a4a5h.o0jt.eastus2.aroapp-hcp.io:443/apis/config.openshift.io/v1/clusterversions/version": tls: failed to verify certificate: x509: certificate is valid for api.a5t3f6u4j8a4a5h.4ufg.eastus2.aroapp-hcp.io, reserved.aroapp-hcp.io, not api.a5t3f6u4j8a4a5h.o0jt.eastus2.aroapp-hcp.io
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:161]: Unexpected error:
    <*url.Error | 0xc00161c840>: 
    Get "https://api.a5t3f6u4j8a4a5h.o0jt.eastus2.aroapp-hcp.io:443/apis/config.openshift.io/v1/clusterversions/version": tls: failed to verify certificate: x509: certificate is valid for api.a5t3f6u4j8a4a5h.4ufg.eastus2.aroapp-hcp.io, reserved.aroapp-hcp.io, not api.a5t3f6u4j8a4a5h.o0jt.eastus2.aroapp-hcp.io
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-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/a2044346239444586496
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 — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e13.33%1 of 30 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsApr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 0 · Apr 16: 0 · Apr 17: 0 · Apr 18: 0 · Apr 19: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/idms_lifecycle.go:231]: Unexpected error:
    <*exported.ResponseError | 0xc0009c4120>: 
    PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/idms-lqclsn/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/idms-e2e-hcp-cluster
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2pov3etqh83nm9qcgs84pchtu7ljs2eo' is in state 'pending_update', can't update"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/idms_lifecycle.go:231]: Unexpected error:
    <*exported.ResponseError | 0xc0009c4120>: 
    PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/idms-lqclsn/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/idms-e2e-hcp-cluster
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2pov3etqh83nm9qcgs84pchtu7ljs2eo' is in state 'pending_update', can't update"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to create an HCP cluster and manage ImageDigestMirrors1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2045683815623430144
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)
e2e13.33%1 of 30 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsApr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 0 · Apr 16: 1 · Apr 17: 0 · Apr 18: 0 · Apr 19: 0none
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