<
Single Day: Jun 11
> Reset
View JSON API

Environment: PROD

Failure patterns: 6 · Failures matched: 16 · Total runs: 11 · Runs affected: 9

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.
Interrupted by User
full failure pattern:
Interrupted by User
Signal: FlakeSignal: Flake — present in 2 prior week(s); spread across 4 days
e2e436.36%4 of 11 job runs affectedFlakeSignal: Flake — present in 2 prior week(s); spread across 4 daysShow trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 2 · Jun 9: 3 · Jun 10: 2 · Jun 11: 4none
Full failure examples (2)
fail [:0]: Interrupted by User
fail [:0]: Interrupted by User
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:37]: Interrupted by User
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:37]: Interrupted by User
Contributing tests (3)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to create an HCP cluster then delete it by deleting the customer resource group1
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2064995434417360896
n/a2064979974896488448
n/a2064892701127479296
n/a2064892559024459776
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)
e2e327.27%3 of 11 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 5none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-5-0-v9zfnv/cluster-nightly-5-0-jq7d6s should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc001510ae0>: 
    failed waiting for cluster="cluster-nightly-5-0-jq7d6s" in resourcegroup="rg-nightly-5-0-v9zfnv" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-5-0-jq7d6s in resource group rg-nightly-5-0-v9zfnv, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-5-0-v9zfnv/cluster-nightly-5-0-jq7d6s should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc001510ae0>: 
    failed waiting for cluster="cluster-nightly-5-0-jq7d6s" in resourcegroup="rg-nightly-5-0-v9zfnv" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-5-0-jq7d6s in resource group rg-nightly-5-0-v9zfnv, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-4-23-krdd6q/cluster-nightly-4-23-q28cpq should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0018073b0>: 
    failed waiting for cluster="cluster-nightly-4-23-q28cpq" in resourcegroup="rg-nightly-4-23-krdd6q" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-q28cpq in resource group rg-nightly-4-23-krdd6q, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-4-23-krdd6q/cluster-nightly-4-23-q28cpq should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0018073b0>: 
    failed waiting for cluster="cluster-nightly-4-23-q28cpq" in resourcegroup="rg-nightly-4-23-krdd6q" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-q28cpq in resource group rg-nightly-4-23-krdd6q, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-4-23-7mghfc/cluster-nightly-4-23-qxb2mc should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0014f5020>: 
    failed waiting for cluster="cluster-nightly-4-23-qxb2mc" in resourcegroup="rg-nightly-4-23-7mghfc" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-qxb2mc in resource group rg-nightly-4-23-7mghfc, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:126]: Swift cluster rg-nightly-4-23-7mghfc/cluster-nightly-4-23-qxb2mc should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0014f5020>: 
    failed waiting for cluster="cluster-nightly-4-23-qxb2mc" in resourcegroup="rg-nightly-4-23-7mghfc" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-nightly-4-23-qxb2mc in resource group rg-nightly-4-23-7mghfc, error: context deadline exceeded
    ...
occurred
Contributing tests (4)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.232
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.01
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallel-ocp-nightlyARO-HCP should be able to perform a control plane and node pool install with OCP nightly channel for 4.231
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallel-ocp-nightlyARO-HCP should be able to perform a control plane and node pool install with OCP nightly channel for 5.01
Affected runs (3)
Date (UTC)Associated PRProw job
n/a2065207457541525504
n/a2065133461022183424
n/a2064999166156738560
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)
e2e327.27%3 of 11 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 4none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:192]: failed to create node pool "np-qdg249" for cluster "cluster-candidate-4-21-qdg249"
Unexpected error:
    <*fmt.wrapErrors | 0xc0009ad380>: 
    failed to create NodePool np-qdg249, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-qdg249 in resource group rg-candidate-4-21-vrs8xc, error: failed waiting for nodepool="np-qdg249" for cluster "cluster-candidate-4-21-qdg249" in resourcegroup="rg-candidate-4-21-vrs8xc" 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-qdg249" for cluster "cluster-candidate-4-21-qdg249"
Unexpected error:
    <*fmt.wrapErrors | 0xc0009ad380>: 
    failed to create NodePool np-qdg249, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-qdg249 in resource group rg-candidate-4-21-vrs8xc, error: failed waiting for nodepool="np-qdg249" for cluster "cluster-candidate-4-21-qdg249" in resourcegroup="rg-candidate-4-21-vrs8xc" 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-bbwmsl" for cluster "cluster-candidate-4-21-bbwmsl"
Unexpected error:
    <*fmt.wrapErrors | 0xc0011f4360>: 
    failed to create NodePool np-bbwmsl, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-bbwmsl in resource group rg-candidate-4-21-tf47dc, error: failed waiting for nodepool="np-bbwmsl" for cluster "cluster-candidate-4-21-bbwmsl" in resourcegroup="rg-candidate-4-21-tf47dc" 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-bbwmsl" for cluster "cluster-candidate-4-21-bbwmsl"
Unexpected error:
    <*fmt.wrapErrors | 0xc0011f4360>: 
    failed to create NodePool np-bbwmsl, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-bbwmsl in resource group rg-candidate-4-21-tf47dc, error: failed waiting for nodepool="np-bbwmsl" for cluster "cluster-candidate-4-21-bbwmsl" in resourcegroup="rg-candidate-4-21-tf47dc" 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-ntc7jm" for cluster "cluster-candidate-4-20-ntc7jm"
Unexpected error:
    <*fmt.wrapErrors | 0xc0008abe00>: 
    failed to create NodePool np-ntc7jm, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-ntc7jm in resource group rg-candidate-4-20-ggl9jk, error: failed waiting for nodepool="np-ntc7jm" for cluster "cluster-candidate-4-20-ntc7jm" in resourcegroup="rg-candidate-4-20-ggl9jk" 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-ntc7jm" for cluster "cluster-candidate-4-20-ntc7jm"
Unexpected error:
    <*fmt.wrapErrors | 0xc0008abe00>: 
    failed to create NodePool np-ntc7jm, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-ntc7jm in resource group rg-candidate-4-20-ggl9jk, error: failed waiting for nodepool="np-ntc7jm" for cluster "cluster-candidate-4-20-ntc7jm" in resourcegroup="rg-candidate-4-20-ggl9jk" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.202
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.212
Affected runs (3)
Date (UTC)Associated PRProw job
n/a2064999166156738560
n/a2064892795172163584
n/a2064892701127479296
ERROR CODE: MultipleErrorsOccurred; detail code InvalidRequestContent; detail message Invalid value: "4.19.33": cannot downgrade from version 4.21.19 to 4.19.33; provider Microsof...
full failure pattern:
ERROR CODE: MultipleErrorsOccurred; detail code InvalidRequestContent; detail message Invalid value: "4.19.33": cannot downgrade from version 4.21.19 to 4.19.33; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior history
e2e19.09%1 of 11 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior historyShow trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 1 · Jun 11: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:750]: failed to update nodepool npdg-421-419 to downgrade target 4.19.33
Unexpected error:
    <*fmt.wrapError | 0xc000f04b20>: 
    failed to start nodepool "npdg-421-419" update in cluster "np-dg-minor-c9l7d4" resourcegroup="rg-np-dg-minor-c9l7d4-jlrlpp": PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-dg-minor-c9l7d4-jlrlpp/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-dg-minor-c9l7d4/nodePools/npdg-421-419
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: MultipleErrorsOccurred
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "MultipleErrorsOccurred",
        "message": "2 errors occurred",
        "details": [
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.19.33\": invalid node pool version 4.19.33: cannot downgrade from current version 4.21.19",
            "target": "properties.version.id"
          },
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.19.33\": cannot downgrade from version 4.21.19 to 4.19.33",
            "target": "properties.version.id"
          }
        ]
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:750]: failed to update nodepool npdg-421-419 to downgrade target 4.19.33
Unexpected error:
    <*fmt.wrapError | 0xc000f04b20>: 
    failed to start nodepool "npdg-421-419" update in cluster "np-dg-minor-c9l7d4" resourcegroup="rg-np-dg-minor-c9l7d4-jlrlpp": PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-dg-minor-c9l7d4-jlrlpp/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-dg-minor-c9l7d4/nodePools/npdg-421-419
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: MultipleErrorsOccurred
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "MultipleErrorsOccurred",
        "message": "2 errors occurred",
        "details": [
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.19.33\": invalid node pool version 4.19.33: cannot downgrade from current version 4.21.19",
            "target": "properties.version.id"
          },
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.19.33\": cannot downgrade from version 4.21.19 to 4.19.33",
            "target": "properties.version.id"
          }
        ]
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should downgrade a nodepool to a lower minor version from 4.21.zLatest to 4.19.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2064890364723990528
ERROR CODE: MultipleErrorsOccurred; detail code InvalidRequestContent; detail message Invalid value: "4.21.18": cannot downgrade from version 4.21.19 to 4.21.18; provider Microsof...
full failure pattern:
ERROR CODE: MultipleErrorsOccurred; detail code InvalidRequestContent; detail message Invalid value: "4.21.18": cannot downgrade from version 4.21.19 to 4.21.18; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior history
e2e19.09%1 of 11 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior historyShow trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 1 · Jun 11: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:619]: failed to update nodepool npdg-4-21 to downgrade target 4.21.18
Unexpected error:
    <*fmt.wrapError | 0xc00099a220>: 
    failed to start nodepool "npdg-4-21" update in cluster "np-downgrade-sh8sbm" resourcegroup="rg-np-downgrade-sh8sbm-8xc2g7": PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-downgrade-sh8sbm-8xc2g7/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-downgrade-sh8sbm/nodePools/npdg-4-21
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: MultipleErrorsOccurred
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "MultipleErrorsOccurred",
        "message": "2 errors occurred",
        "details": [
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.21.18\": invalid node pool version 4.21.18: cannot downgrade from current version 4.21.19",
            "target": "properties.version.id"
          },
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.21.18\": cannot downgrade from version 4.21.19 to 4.21.18",
            "target": "properties.version.id"
          }
        ]
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:619]: failed to update nodepool npdg-4-21 to downgrade target 4.21.18
Unexpected error:
    <*fmt.wrapError | 0xc00099a220>: 
    failed to start nodepool "npdg-4-21" update in cluster "np-downgrade-sh8sbm" resourcegroup="rg-np-downgrade-sh8sbm-8xc2g7": PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-downgrade-sh8sbm-8xc2g7/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-downgrade-sh8sbm/nodePools/npdg-4-21
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: MultipleErrorsOccurred
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "MultipleErrorsOccurred",
        "message": "2 errors occurred",
        "details": [
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.21.18\": invalid node pool version 4.21.18: cannot downgrade from current version 4.21.19",
            "target": "properties.version.id"
          },
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.21.18\": cannot downgrade from version 4.21.19 to 4.21.18",
            "target": "properties.version.id"
          }
        ]
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should downgrade a nodepool version z-stream downgrade from 4.21.zLatest to 4.21.zPrevious1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2064890364723990528
Post "<url>": dial tcp <ip>:<port>: i/o timeout
full failure pattern:
Post "<url>": dial tcp <ip>:<port>: i/o timeout
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e19.09%1 of 11 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 5: 0 · Jun 6: 0 · Jun 7: 0 · Jun 8: 0 · Jun 9: 0 · Jun 10: 0 · Jun 11: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:236]: should be able to create SelfSubjectReview for admin credential 2
Unexpected error:
    <*url.Error | 0xc000999560>: 
    Post "https://api.n1i3e7e9x8g0b6s.ci57.brazilsouth.aroapp-hcp.io:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 74.163.139.192:443: i/o timeout
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:236]: should be able to create SelfSubjectReview for admin credential 2
Unexpected error:
    <*url.Error | 0xc000999560>: 
    Post "https://api.n1i3e7e9x8g0b6s.ci57.brazilsouth.aroapp-hcp.io:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 74.163.139.192:443: i/o timeout
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-prod-e2e-parallelCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2064995434417360896