CIHealth
<
Single Day: Jun 28▾
Last 7 Days Weekly: Jun 22 - Jun 28 Sprint: Jun 22 - Jul 5 Single Day: Jun 28
Custom time window
> Reset
View JSON API

Environment: STG

Failure patterns: 3 · Failures matched: 6 · Total runs: 3 · 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.
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 3 prior week(s); active 1 day(s)
e2e266.67%2 of 3 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsJun 22: 0 · Jun 23: 0 · Jun 24: 0 · Jun 25: 0 · Jun 26: 0 · Jun 27: 0 · Jun 28: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:159]: failed to create node pool "np-qt62hg" for cluster "cluster-nightly-4-22-qt62hg"
Unexpected error:
    <*fmt.wrapErrors | 0xc001963170>: 
    failed to create NodePool np-qt62hg, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-qt62hg in resource group rg-nightly-4-22-89k865, error: failed waiting for nodepool="np-qt62hg" for cluster "cluster-nightly-4-22-qt62hg" in resourcegroup="rg-nightly-4-22-89k865" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:159]: failed to create node pool "np-qt62hg" for cluster "cluster-nightly-4-22-qt62hg"
Unexpected error:
    <*fmt.wrapErrors | 0xc001963170>: 
    failed to create NodePool np-qt62hg, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-qt62hg in resource group rg-nightly-4-22-89k865, error: failed waiting for nodepool="np-qt62hg" for cluster "cluster-nightly-4-22-qt62hg" in resourcegroup="rg-nightly-4-22-89k865" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:214]: failed to create no-AZ nodepool autoscale-noaz with autoscaling
Unexpected error:
    <*fmt.wrapErrors | 0xc000a33ad0>: 
    failed to create NodePool autoscale-noaz, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool autoscale-noaz in resource group np-autoscaling-f2qq9q, error: failed waiting for nodepool="autoscale-noaz" for cluster "np-autoscale-cluster" in resourcegroup="np-autoscaling-f2qq9q" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:214]: failed to create no-AZ nodepool autoscale-noaz with autoscaling
Unexpected error:
    <*fmt.wrapErrors | 0xc000a33ad0>: 
    failed to create NodePool autoscale-noaz, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool autoscale-noaz in resource group np-autoscaling-f2qq9q, error: failed waiting for nodepool="autoscale-noaz" for cluster "np-autoscale-cluster" in resourcegroup="np-autoscaling-f2qq9q" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled up to replica limits1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyARO-HCP should be able to perform a control plane and node pool install with OCP nightly channel for 4.221
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2071368141530730496
n/a2071331624070418432
failed to cleanup resource group: at least one HCP cluster <cluster> to delete: failed waiting for hcpcluster="<cluster>" in resourcegroup="<resource-group>" to finish deleting: c...
full failure pattern:
failed to cleanup resource group: at least one HCP cluster <cluster> to delete: failed waiting for hcpcluster="<cluster>" in resourcegroup="<resource-group>" to finish deleting: context canceled
Signal: IndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)
e2e266.67%2 of 3 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsJun 22: 0 · Jun 23: 0 · Jun 24: 0 · Jun 25: 0 · Jun 26: 0 · Jun 27: 0 · Jun 28: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:283] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc00130e300>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-nfhflv" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:283] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc00130e300>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-nfhflv" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:283] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc0013be438>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="patch-tags-cluster" in resourcegroup="patch-tags-nr68nw" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:283] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc0013be438>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="patch-tags-cluster" in resourcegroup="patch-tags-nr68nw" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelUpdate HCPOpenShiftCluster Positive creates a cluster and updates tags with a PATCH request1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create node pools with ARM64-based VMs1
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2071368141530730496
n/a2071331624070418432
timeout during CreateHCPClusterAndWait; context deadline exceeded
full failure pattern:
timeout during CreateHCPClusterAndWait; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)
e2e133.33%1 of 3 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJun 22: 0 · Jun 23: 0 · Jun 24: 0 · Jun 25: 0 · Jun 26: 0 · Jun 27: 0 · Jun 28: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-4-22-7bcwz9/cluster-candidate-4-22-wmxsmt should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000a1c1b0>: 
    failed to create HCP cluster cluster-candidate-4-22-wmxsmt, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-4-22-wmxsmt in resource group rg-candidate-4-22-7bcwz9, error: failed waiting for cluster="cluster-candidate-4-22-wmxsmt" in resourcegroup="rg-candidate-4-22-7bcwz9" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-4-22-wmxsmt in resource group rg-candidate-4-22-7bcwz9, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-4-22-7bcwz9/cluster-candidate-4-22-wmxsmt should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000a1c1b0>: 
    failed to create HCP cluster cluster-candidate-4-22-wmxsmt, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-4-22-wmxsmt in resource group rg-candidate-4-22-7bcwz9, error: failed waiting for cluster="cluster-candidate-4-22-wmxsmt" in resourcegroup="rg-candidate-4-22-7bcwz9" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-4-22-wmxsmt in resource group rg-candidate-4-22-7bcwz9, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-5-0-wg5rzb/cluster-candidate-5-0-4q5ggx should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0014f0720>: 
    failed to create HCP cluster cluster-candidate-5-0-4q5ggx, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-4q5ggx in resource group rg-candidate-5-0-wg5rzb, error: failed waiting for cluster="cluster-candidate-5-0-4q5ggx" in resourcegroup="rg-candidate-5-0-wg5rzb" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-4q5ggx in resource group rg-candidate-5-0-wg5rzb, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-5-0-wg5rzb/cluster-candidate-5-0-4q5ggx should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0014f0720>: 
    failed to create HCP cluster cluster-candidate-5-0-4q5ggx, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-4q5ggx in resource group rg-candidate-5-0-wg5rzb, error: failed waiting for cluster="cluster-candidate-5-0-4q5ggx" in resourcegroup="rg-candidate-5-0-wg5rzb" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-4q5ggx in resource group rg-candidate-5-0-wg5rzb, error: context deadline exceeded
    ...
occurred
Contributing tests (2)
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
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 5.01
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2071331624070418432