CIHealth
<
Single Day: Jun 13▾
Last 7 Days Weekly: Jun 8 - Jun 14 Sprint: Jun 8 - Jun 21 Single Day: Jun 13
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 3 · Failures matched: 4 · 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 1 prior week(s); active 1 day(s)
e2e266.67%2 of 3 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)Show trend detailsJun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 0 · Jun 12: 0 · Jun 13: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-8gwwzp" for cluster "cluster-candidate-4-20-8gwwzp"
Unexpected error:
    <*fmt.wrapErrors | 0xc000d554d0>: 
    failed to create NodePool np-8gwwzp, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-8gwwzp in resource group rg-candidate-4-20-42lt49, error: failed waiting for nodepool="np-8gwwzp" for cluster "cluster-candidate-4-20-8gwwzp" in resourcegroup="rg-candidate-4-20-42lt49" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-8gwwzp" for cluster "cluster-candidate-4-20-8gwwzp"
Unexpected error:
    <*fmt.wrapErrors | 0xc000d554d0>: 
    failed to create NodePool np-8gwwzp, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-8gwwzp in resource group rg-candidate-4-20-42lt49, error: failed waiting for nodepool="np-8gwwzp" for cluster "cluster-candidate-4-20-8gwwzp" in resourcegroup="rg-candidate-4-20-42lt49" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-zs77cd" for cluster "cluster-candidate-4-20-zs77cd"
Unexpected error:
    <*fmt.wrapErrors | 0xc000a97b30>: 
    failed to create NodePool np-zs77cd, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-zs77cd in resource group rg-candidate-4-20-c5f2pt, error: failed waiting for nodepool="np-zs77cd" for cluster "cluster-candidate-4-20-zs77cd" in resourcegroup="rg-candidate-4-20-c5f2pt" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-zs77cd" for cluster "cluster-candidate-4-20-zs77cd"
Unexpected error:
    <*fmt.wrapErrors | 0xc000a97b30>: 
    failed to create NodePool np-zs77cd, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-zs77cd in resource group rg-candidate-4-20-c5f2pt, error: failed waiting for nodepool="np-zs77cd" for cluster "cluster-candidate-4-20-zs77cd" in resourcegroup="rg-candidate-4-20-c5f2pt" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.202
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2065694033967058944
n/a2065640103975325696
ERROR CODE: InvalidRequestContent; detail message Duplicate ARO-HCP cluster <cluster>. An ARO-HCP cluster <cluster> name 'cidr-connectivity-test', Azure Subscription ID 'XXXXXXXXX...
full failure pattern:
ERROR CODE: InvalidRequestContent; detail message Duplicate ARO-HCP cluster <cluster>. An ARO-HCP cluster <cluster> name 'cidr-connectivity-test', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure resource group <resource-group> 'e2e-cidr-connectivity-mp49x4' already exists; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e133.33%1 of 3 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 0 · Jun 12: 0 · Jun 13: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:149]: failed to create HCP cluster "cidr-connectivity-test" with authorized CIDRs
Unexpected error:
    <*fmt.wrapError | 0xc0008677a0>: 
    failed to create HCP cluster cidr-connectivity-test: failed starting cluster creation "cidr-connectivity-test" in resourcegroup="e2e-cidr-connectivity-mp49x4": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/e2e-cidr-connectivity-mp49x4/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cidr-connectivity-test
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Duplicate ARO-HCP cluster name. An ARO-HCP cluster with name 'cidr-connectivity-test', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure Resource group name 'e2e-cidr-connectivity-mp49x4' already exists"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:149]: failed to create HCP cluster "cidr-connectivity-test" with authorized CIDRs
Unexpected error:
    <*fmt.wrapError | 0xc0008677a0>: 
    failed to create HCP cluster cidr-connectivity-test: failed starting cluster creation "cidr-connectivity-test" in resourcegroup="e2e-cidr-connectivity-mp49x4": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/e2e-cidr-connectivity-mp49x4/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cidr-connectivity-test
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Duplicate ARO-HCP cluster name. An ARO-HCP cluster with name 'cidr-connectivity-test', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure Resource group name 'e2e-cidr-connectivity-mp49x4' already exists"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2065694033967058944
expected <count> ready (and schedulable) nodes, found <count>
full failure pattern:
expected <count> ready (and schedulable) nodes, found <count>
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e133.33%1 of 3 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 0 · Jun 12: 0 · Jun 13: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:231]: failed to verify 3 ready and schedulable nodes for nodepool npupgrade-4-21 after upgrade
Expected success, but got an error:
    <*errors.errorString | 0xc0005a0fa0>: 
    expected 3 ready (and schedulable) nodes in node pool "npupgrade-4-21", found 4
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:231]: failed to verify 3 ready and schedulable nodes for nodepool npupgrade-4-21 after upgrade
Expected success, but got an error:
    <*errors.errorString | 0xc0005a0fa0>: 
    expected 3 ready (and schedulable) nodes in node pool "npupgrade-4-21", found 4
    ...
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should upgrade and update a nodepool from 4.21.z to 4.21.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2065640103975325696