CIHealth
<
Single Day: Apr 3▾
Last 7 Days Weekly: Mar 30 - Apr 5 Sprint: Mar 30 - Apr 12 Single Day: Apr 3
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 3 · Failures matched: 3 · Total runs: 2 · 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)
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsMar 28: 0 · Mar 29: 0 · Mar 30: 0 · Mar 31: 0 · Apr 1: 0 · Apr 2: 0 · Apr 3: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc000b37470>: 
    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-s2z7xg, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-s2z7xg" to finish creating: context deadline exceeded
    {
        msg: "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-s2z7xg, error: failed waiting for nodepool=\"np-1\" for cluster \"private-kv-cluster\" in resourcegroup=\"private-keyvault-s2z7xg\" to finish creating: context deadline exceeded",
        errs: [
            <*errors.errorString | 0xc000340210>{
                s: "timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-s2z7xg",
            },
            <*fmt.wrapError | 0xc000f90d40>{
                msg: "failed waiting for nodepool=\"np-1\" for cluster \"private-kv-cluster\" in resourcegroup=\"private-keyvault-s2z7xg\" to finish creating: context deadline exceeded",
                err: <context.deadlineExceededError>{},
            },
        ],
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc000b37470>: 
    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-s2z7xg, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-s2z7xg" to finish creating: context deadline exceeded
    {
        msg: "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-s2z7xg, error: failed waiting for nodepool=\"np-1\" for cluster \"private-kv-cluster\" in resourcegroup=\"private-keyvault-s2z7xg\" to finish creating: context deadline exceeded",
        errs: [
            <*errors.errorString | 0xc000340210>{
                s: "timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-s2z7xg",
            },
            <*fmt.wrapError | 0xc000f90d40>{
                msg: "failed waiting for nodepool=\"np-1\" for cluster \"private-kv-cluster\" in resourcegroup=\"private-keyvault-s2z7xg\" to finish creating: context deadline exceeded",
                err: <context.deadlineExceededError>{},
            },
        ],
    }
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2040151865483595776
failed to cleanup resource group: failed waiting for resourcegroup="<resource-group>" to finish deleting: context canceled
full failure pattern:
failed to cleanup resource group: failed waiting for resourcegroup="<resource-group>" to finish deleting: context canceled
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMar 28: 0 · Mar 29: 0 · Mar 30: 0 · Mar 31: 0 · Apr 1: 0 · Apr 2: 0 · Apr 3: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:246] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc001238348>: 
    failed to cleanup resource group: failed waiting for resourcegroup="rg-negative-tests-pgqhpg" to finish deleting: context canceled
    {
        errs: [
            <*fmt.wrapError | 0xc001245340>{
                msg: "failed to cleanup resource group: failed waiting for resourcegroup=\"rg-negative-tests-pgqhpg\" to finish deleting: context canceled",
                err: <*fmt.wrapError | 0xc001245320>{
                    msg: "failed waiting for resourcegroup=\"rg-negative-tests-pgqhpg\" to finish deleting: context canceled",
                    err: <*errors.errorString | 0xbee2c60>{
                        s: "context canceled",
                    },
                },
            },
        ],
    }
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:246] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc001238348>: 
    failed to cleanup resource group: failed waiting for resourcegroup="rg-negative-tests-pgqhpg" to finish deleting: context canceled
    {
        errs: [
            <*fmt.wrapError | 0xc001245340>{
                msg: "failed to cleanup resource group: failed waiting for resourcegroup=\"rg-negative-tests-pgqhpg\" to finish deleting: context canceled",
                err: <*fmt.wrapError | 0xc001245320>{
                    msg: "failed waiting for resourcegroup=\"rg-negative-tests-pgqhpg\" to finish deleting: context canceled",
                    err: <*errors.errorString | 0xbee2c60>{
                        s: "context canceled",
                    },
                },
            },
        ],
    }
occurred  
fail [:0]: A node timeout occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should not be able to perform various invalid operations on cluster resources1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2040151865483595776
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 — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMar 28: 0 · Mar 29: 0 · Mar 30: 0 · Mar 31: 0 · Apr 1: 0 · Apr 2: 0 · Apr 3: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc001b03140>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-96sc9p" to finish creating: context deadline exceeded
    {
        msg: "failed waiting for nodepool=\"cilium-np\" for cluster \"cilium-cluster\" in resourcegroup=\"e2e-cilium-96sc9p\" to finish creating: context deadline exceeded",
        err: <context.deadlineExceededError>{},
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc001b03140>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-96sc9p" to finish creating: context deadline exceeded
    {
        msg: "failed waiting for nodepool=\"cilium-np\" for cluster \"cilium-cluster\" in resourcegroup=\"e2e-cilium-96sc9p\" to finish creating: context deadline exceeded",
        err: <context.deadlineExceededError>{},
    }
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2040191555695808512