CIHealth
<
Single Day: Feb 28▾
Last 7 Days Weekly: Feb 23 - Mar 1 Sprint: Feb 16 - Mar 1 Single Day: Feb 28
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 5 · Failures matched: 101 · Total runs: 7 · Runs affected: 6

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: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e571.43%5 of 7 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsFeb 22: 0 · Feb 23: 0 · Feb 24: 0 · Feb 25: 0 · Feb 26: 0 · Feb 27: 0 · Feb 28: 70none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:83]: Unexpected error:
    <*fmt.wrapErrors | 0xc000a090b0>: 
    failed to create HCP cluster np-autoscale-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: failed waiting for cluster="np-autoscale-cluster" in resourcegroup="np-autoscaling-zvfvz7" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: context deadline exceeded
    {
        msg: "failed to create HCP cluster np-autoscale-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: failed waiting for cluster=\"np-autoscale-cluster\" in resourcegroup=\"np-autoscaling-zvfvz7\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: context deadline exceeded",
        errs: [
            <*errors.errorString | 0xc0011d6b30>{
                s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7",
            },
            <*fmt.wrapErrors | 0xc000a08960>{
                msg: "failed waiting for cluster=\"np-autoscale-cluster\" in resourcegroup=\"np-autoscaling-zvfvz7\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: context deadline exceeded",
                errs: [
                    <*errors.errorString | 0xc0011d6b30>{
                        s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7",
                    },
                    <context.deadlineExceededError>{},
                ],
            },
        ],
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_autoscaling.go:83]: Unexpected error:
    <*fmt.wrapErrors | 0xc000a090b0>: 
    failed to create HCP cluster np-autoscale-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: failed waiting for cluster="np-autoscale-cluster" in resourcegroup="np-autoscaling-zvfvz7" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: context deadline exceeded
    {
        msg: "failed to create HCP cluster np-autoscale-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: failed waiting for cluster=\"np-autoscale-cluster\" in resourcegroup=\"np-autoscaling-zvfvz7\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: context deadline exceeded",
        errs: [
            <*errors.errorString | 0xc0011d6b30>{
                s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7",
            },
            <*fmt.wrapErrors | 0xc000a08960>{
                msg: "failed waiting for cluster=\"np-autoscale-cluster\" in resourcegroup=\"np-autoscaling-zvfvz7\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7, error: context deadline exceeded",
                errs: [
                    <*errors.errorString | 0xc0011d6b30>{
                        s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-autoscale-cluster in resource group np-autoscaling-zvfvz7",
                    },
                    <context.deadlineExceededError>{},
                ],
            },
        ],
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_nodepool_osdisk.go:80]: Unexpected error:
    <*fmt.wrapErrors | 0xc0009ac5d0>: 
    failed to create HCP cluster hcp-cluster-np-128, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: failed waiting for cluster="hcp-cluster-np-128" in resourcegroup="clusternp128-tlzzqm" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: context deadline exceeded
    {
        msg: "failed to create HCP cluster hcp-cluster-np-128, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: failed waiting for cluster=\"hcp-cluster-np-128\" in resourcegroup=\"clusternp128-tlzzqm\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: context deadline exceeded",
        errs: [
            <*errors.errorString | 0xc000a21ca0>{
                s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm",
            },
            <*fmt.wrapErrors | 0xc0009ac5a0>{
                msg: "failed waiting for cluster=\"hcp-cluster-np-128\" in resourcegroup=\"clusternp128-tlzzqm\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: context deadline exceeded",
                errs: [
                    <*errors.errorString | 0xc000a21ca0>{
                        s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm",
                    },
                    <context.deadlineExceededError>{},
                ],
            },
        ],
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_nodepool_osdisk.go:80]: Unexpected error:
    <*fmt.wrapErrors | 0xc0009ac5d0>: 
    failed to create HCP cluster hcp-cluster-np-128, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: failed waiting for cluster="hcp-cluster-np-128" in resourcegroup="clusternp128-tlzzqm" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: context deadline exceeded
    {
        msg: "failed to create HCP cluster hcp-cluster-np-128, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: failed waiting for cluster=\"hcp-cluster-np-128\" in resourcegroup=\"clusternp128-tlzzqm\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: context deadline exceeded",
        errs: [
            <*errors.errorString | 0xc000a21ca0>{
                s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm",
            },
            <*fmt.wrapErrors | 0xc0009ac5a0>{
                msg: "failed waiting for cluster=\"hcp-cluster-np-128\" in resourcegroup=\"clusternp128-tlzzqm\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm, error: context deadline exceeded",
                errs: [
                    <*errors.errorString | 0xc000a21ca0>{
                        s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster hcp-cluster-np-128 in resource group clusternp128-tlzzqm",
                    },
                    <context.deadlineExceededError>{},
                ],
            },
        ],
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_cluster_create.go:89]: Unexpected error:
    <*fmt.wrapErrors | 0xc000bf6cc0>: 
    failed to create HCP cluster disabled-image-registry-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: failed waiting for cluster="disabled-image-registry-hcp-cluster" in resourcegroup="disabled-image-registry-4gtcw7" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: context deadline exceeded
    {
        msg: "failed to create HCP cluster disabled-image-registry-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: failed waiting for cluster=\"disabled-image-registry-hcp-cluster\" in resourcegroup=\"disabled-image-registry-4gtcw7\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: context deadline exceeded",
        errs: [
            <*errors.errorString | 0xc000f76eb0>{
                s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7",
            },
            <*fmt.wrapErrors | 0xc000bf6c60>{
                msg: "failed waiting for cluster=\"disabled-image-registry-hcp-cluster\" in resourcegroup=\"disabled-image-registry-4gtcw7\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: context deadline exceeded",
                errs: [
                    <*errors.errorString | 0xc000f76eb0>{
                        s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7",
                    },
                    <context.deadlineExceededError>{},
                ],
            },
        ],
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_cluster_create.go:89]: Unexpected error:
    <*fmt.wrapErrors | 0xc000bf6cc0>: 
    failed to create HCP cluster disabled-image-registry-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: failed waiting for cluster="disabled-image-registry-hcp-cluster" in resourcegroup="disabled-image-registry-4gtcw7" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: context deadline exceeded
    {
        msg: "failed to create HCP cluster disabled-image-registry-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: failed waiting for cluster=\"disabled-image-registry-hcp-cluster\" in resourcegroup=\"disabled-image-registry-4gtcw7\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: context deadline exceeded",
        errs: [
            <*errors.errorString | 0xc000f76eb0>{
                s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7",
            },
            <*fmt.wrapErrors | 0xc000bf6c60>{
                msg: "failed waiting for cluster=\"disabled-image-registry-hcp-cluster\" in resourcegroup=\"disabled-image-registry-4gtcw7\" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7, error: context deadline exceeded",
                errs: [
                    <*errors.errorString | 0xc000f76eb0>{
                        s: "timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster disabled-image-registry-hcp-cluster in resource group disabled-image-registry-4gtcw7",
                    },
                    <context.deadlineExceededError>{},
                ],
            },
        ],
    }
occurred
Contributing tests (17)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create a cluster with an external auth config and get the external auth config5
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster5
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster and manage pull secrets5
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelUpdate HCPOpenShiftCluster Positive creates a cluster and updates tags with a PATCH request5
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster with Image Registry not present4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster with back-level version 4.194
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster with custom autoscaling4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to list HCP clusters without node pools at both subscription and resource group levels4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should create an HCP cluster and validate TLS certificates4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should not be able to reuse subnets and NSGs between clusters4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should respect cluster-wide node limits with nodepool autoscaling4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelUpdate HCPOpenShiftCluster Negative creates a cluster and fails to update its name with a PATCH request4
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster and custom node pool osDisk size3
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create node pools with ARM64-based VMs3
Affected runs (5)
Date (UTC)Associated PRProw job
n/a2027848626440507392
n/a2027846996605276160
n/a2027733643316695040
n/a2027641115875741696
n/a2027616099490598912
Interrupted by User
full failure pattern:
Interrupted by User
Signal: IndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior history
e2e571.43%5 of 7 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior historyShow trend detailsFeb 22: 0 · Feb 23: 0 · Feb 24: 0 · Feb 25: 1 · Feb 26: 0 · Feb 27: 0 · Feb 28: 21none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_nsg_subnet_reuse.go:30]: Interrupted by User
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_nsg_subnet_reuse.go:30]: Interrupted by User
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:35]: Interrupted by User
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:35]: Interrupted by User
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_version_backlevel.go:48]: Interrupted by User
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_version_backlevel.go:48]: Interrupted by User
Contributing tests (15)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group5
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster and custom node pool osDisk size2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create node pools with ARM64-based VMs2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster with Image Registry not present1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster with back-level version 4.191
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to create an HCP cluster with custom autoscaling1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to list HCP clusters without node pools at both subscription and resource group levels1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should create an HCP cluster and validate TLS certificates1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should not be able to reuse subnets and NSGs between clusters1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should respect cluster-wide node limits with nodepool autoscaling1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelUpdate HCPOpenShiftCluster Negative creates a cluster and fails to update its name with a PATCH request1
Affected runs (5)
Date (UTC)Associated PRProw job
n/a2027848626440507392
n/a2027846996605276160
n/a2027733643316695040
n/a2027641115875741696
n/a2027616099490598912
failed waiting for deployment "aro-hcp-demo" in resourcegroup="<resource-group>" to finish: context deadline exceeded
full failure pattern:
failed waiting for deployment "aro-hcp-demo" in resourcegroup="<resource-group>" to finish: context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e571.43%5 of 7 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsFeb 22: 0 · Feb 23: 0 · Feb 24: 0 · Feb 25: 0 · Feb 26: 0 · Feb 27: 0 · Feb 28: 5none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:96]: Unexpected error:
    <*fmt.wrapError | 0xc0014122e0>: 
    failed waiting for deployment "aro-hcp-demo" in resourcegroup="gpu-nodepools-NC4asT4v3-dhsjcz" to finish: context deadline exceeded
    {
        msg: "failed waiting for deployment \"aro-hcp-demo\" in resourcegroup=\"gpu-nodepools-NC4asT4v3-dhsjcz\" to finish: context deadline exceeded",
        err: <context.deadlineExceededError>{},
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:96]: Unexpected error:
    <*fmt.wrapError | 0xc0014122e0>: 
    failed waiting for deployment "aro-hcp-demo" in resourcegroup="gpu-nodepools-NC4asT4v3-dhsjcz" to finish: context deadline exceeded
    {
        msg: "failed waiting for deployment \"aro-hcp-demo\" in resourcegroup=\"gpu-nodepools-NC4asT4v3-dhsjcz\" to finish: context deadline exceeded",
        err: <context.deadlineExceededError>{},
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:96]: Unexpected error:
    <*fmt.wrapError | 0xc0009a0020>: 
    failed waiting for deployment "aro-hcp-demo" in resourcegroup="gpu-nodepools-NC4asT4v3-mb47tb" to finish: context deadline exceeded
    {
        msg: "failed waiting for deployment \"aro-hcp-demo\" in resourcegroup=\"gpu-nodepools-NC4asT4v3-mb47tb\" to finish: context deadline exceeded",
        err: <context.deadlineExceededError>{},
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:96]: Unexpected error:
    <*fmt.wrapError | 0xc0009a0020>: 
    failed waiting for deployment "aro-hcp-demo" in resourcegroup="gpu-nodepools-NC4asT4v3-mb47tb" to finish: context deadline exceeded
    {
        msg: "failed waiting for deployment \"aro-hcp-demo\" in resourcegroup=\"gpu-nodepools-NC4asT4v3-mb47tb\" to finish: context deadline exceeded",
        err: <context.deadlineExceededError>{},
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:96]: Unexpected error:
    <*fmt.wrapError | 0xc000884180>: 
    failed waiting for deployment "aro-hcp-demo" in resourcegroup="gpu-nodepools-NC4asT4v3-jfrsd6" to finish: context deadline exceeded
    {
        msg: "failed waiting for deployment \"aro-hcp-demo\" in resourcegroup=\"gpu-nodepools-NC4asT4v3-jfrsd6\" to finish: context deadline exceeded",
        err: <context.deadlineExceededError>{},
    }
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/gpu_nodepools_create_delete.go:96]: Unexpected error:
    <*fmt.wrapError | 0xc000884180>: 
    failed waiting for deployment "aro-hcp-demo" in resourcegroup="gpu-nodepools-NC4asT4v3-jfrsd6" to finish: context deadline exceeded
    {
        msg: "failed waiting for deployment \"aro-hcp-demo\" in resourcegroup=\"gpu-nodepools-NC4asT4v3-jfrsd6\" to finish: context deadline exceeded",
        err: <context.deadlineExceededError>{},
    }
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelHCP Nodepools GPU instances creates and deletes vm type NC4asT4v3 in a single cluster5
Affected runs (5)
Date (UTC)Associated PRProw job
n/a2027848626440507392
n/a2027846996605276160
n/a2027733643316695040
n/a2027641115875741696
n/a2027616099490598912
Cluster should become ready within 45 minutes
full failure pattern:
Cluster should become ready within 45 minutes
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e457.14%4 of 7 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsFeb 22: 0 · Feb 23: 0 · Feb 24: 0 · Feb 25: 0 · Feb 26: 0 · Feb 27: 0 · Feb 28: 4none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:158]: Timed out after 2700.000s.
Cluster should become ready within 45 minutes
Expected
    <bool>: false
to be true
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:158]: Timed out after 2700.000s.
Cluster should become ready within 45 minutes
Expected
    <bool>: false
to be true
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:158]: Timed out after 2700.344s.
Cluster should become ready within 45 minutes
Expected
    <bool>: false
to be true
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:158]: Timed out after 2700.344s.
Cluster should become ready within 45 minutes
Expected
    <bool>: false
to be true
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallelCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle4
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2027848626440507392
n/a2027846996605276160
n/a2027641115875741696
n/a2027616099490598912
ERROR CODE: Conflict; detail message Cannot update resource while resource is "provisioning"; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: Conflict; detail message Cannot update resource while resource is "provisioning"; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e114.29%1 of 7 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsFeb 22: 0 · Feb 23: 0 · Feb 24: 0 · Feb 25: 0 · Feb 26: 0 · Feb 27: 0 · Feb 28: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_pullsecret.go:112]: Unexpected error:
    <*fmt.wrapError | 0xc00047c640>: 
    failed to create NodePool np-1: failed starting nodepool creation "np-1" for cluster "pullsecret-hcp-cluster" in resourcegroup="pullsecret-test-q2kh8p": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1
    --------------------------------------------------------------------------------
    RESPONSE 409: 409 Conflict
    ERROR CODE: Conflict
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "Conflict",
        "message": "Cannot update resource while resource is \"provisioning\"",
        "target": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1"
      }
    }
    --------------------------------------------------------------------------------
    
    {
        msg: "failed to create NodePool np-1: failed starting nodepool creation \"np-1\" for cluster \"pullsecret-hcp-cluster\" in resourcegroup=\"pullsecret-test-q2kh8p\": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: Conflict\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"Conflict\",\n    \"message\": \"Cannot update resource while resource is \\\"provisioning\\\"\",\n    \"target\": \"/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1\"\n  }\n}\n--------------------------------------------------------------------------------\n",
        err: <*fmt.wrapError | 0xc00047c620>{
            msg: "failed starting nodepool creation \"np-1\" for cluster \"pullsecret-hcp-cluster\" in resourcegroup=\"pullsecret-test-q2kh8p\": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: Conflict\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"Conflict\",\n    \"message\": \"Cannot update resource while resource is \\\"provisioning\\\"\",\n    \"target\": \"/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1\"\n  }\n}\n--------------------------------------------------------------------------------\n",
            err: <*exported.ResponseError | 0xc000da2840>{
                ErrorCode: "Conflict",
                StatusCode: 409,
                RawResponse: {
                    Status: "409 Conflict",
                    StatusCode: 409,
                    Proto: "HTTP/2.0",
                    ProtoMajor: 2,
                    ProtoMinor: 0,
                    Header: {
                        "Cache-Control": ["no-cache"],
                        "Content-Length": ["337"],
                        "X-Ms-Error-Code": ["Conflict"],
                        "X-Ms-Request-Id": [
                            "4ed37b5a-b4c0-4770-a28e-c6490ea6c312",
                        ],
                        "X-Msedge-Ref": [
                            "Ref A: 43729C327091453782F1D7DDE5C7DAA5 Ref B: CHI261140503060 Ref C: 2026-02-28T04:05:08Z",
                        ],
                        "X-Envoy-Upstream-Service-Time": ["147"],
                        "X-Ms-Ratelimit-Remaining-Subscription-Global-Writes": ["2999"],
                        "X-Ms-Correlation-Request-Id": [
                            "8145a09b-5ba1-4659-a364-95e4ef0bdd6a",
                        ],
                        "X-Ms-Routing-Request-Id": [
                            "UKSOUTH:20260228T040509Z:8145a09b-5ba1-4659-a364-95e4ef0bdd6a",
                        ],
                        "Strict-Transport-Security": [
                            "max-age=31536000; includeSubDomains",
                        ],
                        "X-Cache": ["CONFIG_NOCACHE"],
                        "Content-Type": ["application/json"],
                        "X-Ms-Ratelimit-Remaining-Subscription-Writes": ["199"],
                        "Date": [
                            "Sat, 28 Feb 2026 04:05:08 GMT",
                        ],
                        "Pragma": ["no-cache"],
                        "Expires"...

Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_pullsecret.go:112]: Unexpected error:
    <*fmt.wrapError | 0xc00047c640>: 
    failed to create NodePool np-1: failed starting nodepool creation "np-1" for cluster "pullsecret-hcp-cluster" in resourcegroup="pullsecret-test-q2kh8p": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1
    --------------------------------------------------------------------------------
    RESPONSE 409: 409 Conflict
    ERROR CODE: Conflict
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "Conflict",
        "message": "Cannot update resource while resource is \"provisioning\"",
        "target": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1"
      }
    }
    --------------------------------------------------------------------------------
    
    {
        msg: "failed to create NodePool np-1: failed starting nodepool creation \"np-1\" for cluster \"pullsecret-hcp-cluster\" in resourcegroup=\"pullsecret-test-q2kh8p\": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: Conflict\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"Conflict\",\n    \"message\": \"Cannot update resource while resource is \\\"provisioning\\\"\",\n    \"target\": \"/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1\"\n  }\n}\n--------------------------------------------------------------------------------\n",
        err: <*fmt.wrapError | 0xc00047c620>{
            msg: "failed starting nodepool creation \"np-1\" for cluster \"pullsecret-hcp-cluster\" in resourcegroup=\"pullsecret-test-q2kh8p\": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: Conflict\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"Conflict\",\n    \"message\": \"Cannot update resource while resource is \\\"provisioning\\\"\",\n    \"target\": \"/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/pullsecret-test-q2kh8p/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/pullsecret-hcp-cluster/nodePools/np-1\"\n  }\n}\n--------------------------------------------------------------------------------\n",
            err: <*exported.ResponseError | 0xc000da2840>{
                ErrorCode: "Conflict",
                StatusCode: 409,
                RawResponse: {
                    Status: "409 Conflict",
                    StatusCode: 409,
                    Proto: "HTTP/2.0",
                    ProtoMajor: 2,
                    ProtoMinor: 0,
                    Header: {
                        "Cache-Control": ["no-cache"],
                        "Content-Length": ["337"],
                        "X-Ms-Error-Code": ["Conflict"],
                        "X-Ms-Request-Id": [
                            "4ed37b5a-b4c0-4770-a28e-c6490ea6c312",
                        ],
                        "X-Msedge-Ref": [
                            "Ref A: 43729C327091453782F1D7DDE5C7DAA5 Ref B: CHI261140503060 Ref C: 2026-02-28T04:05:08Z",
                        ],
                        "X-Envoy-Upstream-Service-Time": ["147"],
                        "X-Ms-Ratelimit-Remaining-Subscription-Global-Writes": ["2999"],
                        "X-Ms-Correlation-Request-Id": [
                            "8145a09b-5ba1-4659-a364-95e4ef0bdd6a",
                        ],
                        "X-Ms-Routing-Request-Id": [
                            "UKSOUTH:20260228T040509Z:8145a09b-5ba1-4659-a364-95e4ef0bdd6a",
                        ],
                        "Strict-Transport-Security": [
                            "max-age=31536000; includeSubDomains",
                        ],
                        "X-Cache": ["CONFIG_NOCACHE"],
                        "Content-Type": ["application/json"],
                        "X-Ms-Ratelimit-Remaining-Subscription-Writes": ["199"],
                        "Date": [
                            "Sat, 28 Feb 2026 04:05:08 GMT",
                        ],
                        "Pragma": ["no-cache"],
                        "Expires"...

Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

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 pull secrets1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2027586348956782592