<
Weekly: Jul 13 - Jul 19
> Reset
View JSON API

Environment: STG

Failure patterns: 9 · Failures matched: 184 · Total runs: 20 · Runs affected: 13

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: FlakeSignal: Flake — present in 4 prior week(s); spread across 4 days
e2e525.00%5 of 20 job runs affectedFlakeSignal: Flake — present in 4 prior week(s); spread across 4 daysShow trend detailsJul 12: 0 · Jul 13: 2 · Jul 14: 0 · Jul 15: 0 · Jul 16: 2 · Jul 17: 1 · Jul 18: 0 · Jul 19: 1none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-nightly-5-0-9trqdr/cluster-nightly-5-0-g2s25g should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000abc4b0>: 
    failed to create HCP cluster cluster-nightly-5-0-g2s25g, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-g2s25g in resource group rg-nightly-5-0-9trqdr, error: failed waiting for cluster="cluster-nightly-5-0-g2s25g" in resourcegroup="rg-nightly-5-0-9trqdr" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-g2s25g in resource group rg-nightly-5-0-9trqdr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-nightly-5-0-9trqdr/cluster-nightly-5-0-g2s25g should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000abc4b0>: 
    failed to create HCP cluster cluster-nightly-5-0-g2s25g, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-g2s25g in resource group rg-nightly-5-0-9trqdr, error: failed waiting for cluster="cluster-nightly-5-0-g2s25g" in resourcegroup="rg-nightly-5-0-9trqdr" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-g2s25g in resource group rg-nightly-5-0-9trqdr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-nightly-5-0-j7trwc/cluster-nightly-5-0-ttk5lt should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0014f2c60>: 
    failed to create HCP cluster cluster-nightly-5-0-ttk5lt, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-ttk5lt in resource group rg-nightly-5-0-j7trwc, error: failed waiting for cluster="cluster-nightly-5-0-ttk5lt" in resourcegroup="rg-nightly-5-0-j7trwc" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-ttk5lt in resource group rg-nightly-5-0-j7trwc, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-nightly-5-0-j7trwc/cluster-nightly-5-0-ttk5lt should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc0014f2c60>: 
    failed to create HCP cluster cluster-nightly-5-0-ttk5lt, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-ttk5lt in resource group rg-nightly-5-0-j7trwc, error: failed waiting for cluster="cluster-nightly-5-0-ttk5lt" in resourcegroup="rg-nightly-5-0-j7trwc" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-ttk5lt in resource group rg-nightly-5-0-j7trwc, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:459]: failed to create HCP cluster np-skip-minor-v2p4pj at version 4.22.5
Unexpected error:
    <*fmt.wrapErrors | 0xc0016c5230>: 
    failed to create HCP cluster np-skip-minor-v2p4pj, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-skip-minor-v2p4pj in resource group rg-np-skip-minor-v2p4pj-9xtp8n, error: failed waiting for cluster="np-skip-minor-v2p4pj" in resourcegroup="rg-np-skip-minor-v2p4pj-9xtp8n" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-skip-minor-v2p4pj in resource group rg-np-skip-minor-v2p4pj-9xtp8n, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:459]: failed to create HCP cluster np-skip-minor-v2p4pj at version 4.22.5
Unexpected error:
    <*fmt.wrapErrors | 0xc0016c5230>: 
    failed to create HCP cluster np-skip-minor-v2p4pj, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-skip-minor-v2p4pj in resource group rg-np-skip-minor-v2p4pj-9xtp8n, error: failed waiting for cluster="np-skip-minor-v2p4pj" in resourcegroup="rg-np-skip-minor-v2p4pj-9xtp8n" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-skip-minor-v2p4pj in resource group rg-np-skip-minor-v2p4pj-9xtp8n, error: context deadline exceeded
    ...
occurred
Contributing tests (4)
Failed AtJobTestSupport
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 5.03
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should downgrade a nodepool version z-stream downgrade from 4.21.zLatest to 4.21.zPrevious1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should upgrade a nodepool skipping one minor version (+2) from 4.20.z to 4.22.zLatest1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.211
Affected runs (5)
Date (UTC)Associated PRProw job
n/a2078978406782865408
n/a2078253416945029120
n/a2077854502303567872
n/a2076804081216655360
n/a2076486900469731328
ERROR CODE: InvalidRequestContent; detail message Invalid value: "aro-hcp.experimental.cluster.max-creation-duration": unrecognized experimental tag; provider Microsoft.RedHatOpen...
full failure pattern:
ERROR CODE: InvalidRequestContent; detail message Invalid value: "aro-hcp.experimental.cluster.max-creation-duration": unrecognized experimental tag; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 3 day(s) — New failure pattern — no prior history
e2e420.00%4 of 20 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 3 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 0 · Jul 15: 39 · Jul 16: 82 · Jul 17: 43 · Jul 18: 0 · Jul 19: 0none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:132]: failed to create HCP cluster np-version-upgrade-cluster-qbqnw4 with version 4.20.30
Unexpected error:
    <*fmt.wrapError | 0xc0007076c0>: 
    failed to create HCP cluster np-version-upgrade-cluster-qbqnw4: failed starting cluster creation "np-version-upgrade-cluster-qbqnw4" in resourcegroup="rg-np-version-upgrade-qbqnw4-f22tkr": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-version-upgrade-qbqnw4-f22tkr/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-version-upgrade-cluster-qbqnw4
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Invalid value: \"aro-hcp.experimental.cluster.max-creation-duration\": unrecognized experimental tag",
        "target": "tags[aro-hcp.experimental.cluster.max-creation-duration]"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:132]: failed to create HCP cluster np-version-upgrade-cluster-qbqnw4 with version 4.20.30
Unexpected error:
    <*fmt.wrapError | 0xc0007076c0>: 
    failed to create HCP cluster np-version-upgrade-cluster-qbqnw4: failed starting cluster creation "np-version-upgrade-cluster-qbqnw4" in resourcegroup="rg-np-version-upgrade-qbqnw4-f22tkr": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-version-upgrade-qbqnw4-f22tkr/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-version-upgrade-cluster-qbqnw4
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Invalid value: \"aro-hcp.experimental.cluster.max-creation-duration\": unrecognized experimental tag",
        "target": "tags[aro-hcp.experimental.cluster.max-creation-duration]"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-5-0-ndtxgh/cluster-candidate-5-0-xgpxsl should provision
Unexpected error:
    <*fmt.wrapError | 0xc000be82c0>: 
    failed to create HCP cluster cluster-candidate-5-0-xgpxsl: failed starting cluster creation "cluster-candidate-5-0-xgpxsl" in resourcegroup="rg-candidate-5-0-ndtxgh": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-candidate-5-0-ndtxgh/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-candidate-5-0-xgpxsl
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Invalid value: \"aro-hcp.experimental.cluster.max-creation-duration\": unrecognized experimental tag",
        "target": "tags[aro-hcp.experimental.cluster.max-creation-duration]"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-5-0-ndtxgh/cluster-candidate-5-0-xgpxsl should provision
Unexpected error:
    <*fmt.wrapError | 0xc000be82c0>: 
    failed to create HCP cluster cluster-candidate-5-0-xgpxsl: failed starting cluster creation "cluster-candidate-5-0-xgpxsl" in resourcegroup="rg-candidate-5-0-ndtxgh": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-candidate-5-0-ndtxgh/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-candidate-5-0-xgpxsl
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Invalid value: \"aro-hcp.experimental.cluster.max-creation-duration\": unrecognized experimental tag",
        "target": "tags[aro-hcp.experimental.cluster.max-creation-duration]"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:109]: failed to create HCP cluster "cluster-zstream-4-20-lh6462" with version 4.20.28 on candidate channel
Unexpected error:
    <*fmt.wrapError | 0xc000e051e0>: 
    failed to create HCP cluster cluster-zstream-4-20-lh6462: failed starting cluster creation "cluster-zstream-4-20-lh6462" in resourcegroup="rg-zstream-upgrade-4-20-sxvg5j": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-zstream-upgrade-4-20-sxvg5j/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-zstream-4-20-lh6462
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Invalid value: \"aro-hcp.experimental.cluster.max-creation-duration\": unrecognized experimental tag",
        "target": "tags[aro-hcp.experimental.cluster.max-creation-duration]"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:109]: failed to create HCP cluster "cluster-zstream-4-20-lh6462" with version 4.20.28 on candidate channel
Unexpected error:
    <*fmt.wrapError | 0xc000e051e0>: 
    failed to create HCP cluster cluster-zstream-4-20-lh6462: failed starting cluster creation "cluster-zstream-4-20-lh6462" in resourcegroup="rg-zstream-upgrade-4-20-sxvg5j": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-zstream-upgrade-4-20-sxvg5j/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-zstream-4-20-lh6462
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Invalid value: \"aro-hcp.experimental.cluster.max-creation-duration\": unrecognized experimental tag",
        "target": "tags[aro-hcp.experimental.cluster.max-creation-duration]"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (82)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO HCP Service should successfully provision cluster when MI role assignments are added after cluster creation2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.202
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.212
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.222
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.02
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create a HCP cluster and use cilium CNI plugin2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create a cluster with an external auth config and get the external auth config2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled up to replica limits2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster and custom node pool osDisk size2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster and manage ImageDigestMirrors2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster and manage pull secrets2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster then delete it by deleting the customer resource group2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster with Image Registry not present2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster with custom autoscaling2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create node pools with ARM64-based VMs2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to forward control plane logs to a storage account and Event Hub via shoebox diagnostic settings2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to update node pool labels and taints2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to use workload identity via the cluster OIDC issuer URL2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should create an HCP cluster and validate TLS certificates2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should downgrade a nodepool to a lower minor version from 4.21.zLatest to 4.19.zLatest2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should downgrade a nodepool version z-stream downgrade from 4.21.zLatest to 4.21.zPrevious2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should not be able to perform various invalid operations on cluster resources2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should not be able to reuse subnets and NSGs between clusters2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should respect cluster-wide node limits with nodepool autoscaling2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should upgrade a nodepool skipping one minor version (+2) from 4.20.z to 4.22.zLatest2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should upgrade a nodepool to a version without Cincinnati upgrade edge z-stream upgrade without Cincinnati edge in 4.202
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.20.zLatest2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.21.zLatest2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should upgrade and update a nodepool from 4.21.z to 4.21.zLatest2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelFIPS Mode Support with ExperimentalReleaseFeatures AFEC registered should create an HCP cluster with FIPS mode enabled via experimental tag2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelNodepool Ephemeral OS Disk should create a nodepool with ephemeral OS disk when autoRepair is enabled2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.192
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.202
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.212
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.222
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelUpdate HCPOpenShiftCluster Negative creates a cluster and fails to update its name with a PATCH request2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelUpdate HCPOpenShiftCluster Positive creates a cluster and updates tags with a PATCH request2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyARO HCP Service should successfully provision cluster when MI role assignments are added after cluster creation2
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.202
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.212
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.222
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.232
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 5.02
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyAuthorized CIDRs Connectivity should allow API access only from authorized VM IP2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create a HCP cluster and use cilium CNI plugin2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create a cluster with an external auth config and get the external auth config2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled up to replica limits2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create an HCP cluster and custom node pool osDisk size2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create an HCP cluster and manage ImageDigestMirrors2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create an HCP cluster and manage pull secrets2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create an HCP cluster then delete it by deleting the customer resource group2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create an HCP cluster with Image Registry not present2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create an HCP cluster with custom autoscaling2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create node pools with ARM64-based VMs2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to forward control plane logs to a storage account and Event Hub via shoebox diagnostic settings2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to lifecycle and confirm external auth on a cluster2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to update node pool labels and taints2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to use workload identity via the cluster OIDC issuer URL2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should create an HCP cluster and validate TLS certificates2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should downgrade a nodepool to a lower minor version from 4.21.zLatest to 4.19.zLatest2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should not be able to perform various invalid operations on cluster resources2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should not be able to reuse subnets and NSGs between clusters2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should respect cluster-wide node limits with nodepool autoscaling2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should upgrade a nodepool skipping one minor version (+2) from 4.20.z to 4.22.zLatest2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyFIPS Mode Support with ExperimentalReleaseFeatures AFEC registered should create an HCP cluster with FIPS mode enabled via experimental tag2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyNodepool Ephemeral OS Disk should create a nodepool with ephemeral OS disk when autoRepair is enabled2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.192
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.202
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.212
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.222
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyUpdate HCPOpenShiftCluster Negative creates a cluster and fails to update its name with a PATCH request2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyUpdate HCPOpenShiftCluster Positive creates a cluster and updates tags with a PATCH request2
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2077936350778101760
n/a2077891050826895360
n/a2077574106819072000
n/a2077528808046465024
error should indicate FIPS value must be true or false
full failure pattern:
error should indicate FIPS value must be true or false
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 3 day(s)
e2e420.00%4 of 20 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 3 day(s)Show trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 0 · Jul 15: 1 · Jul 16: 2 · Jul 17: 1 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_fips_mode.go:203]: error should indicate FIPS value must be true or false
Expected
    <string>: ...
to contain substring
    <string>: ...
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_fips_mode.go:203]: error should indicate FIPS value must be true or false
Expected
    <string>: ...
to contain substring
    <string>: ...
Contributing tests (2)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelFIPS Mode Support with ExperimentalReleaseFeatures AFEC registered should reject an HCP cluster creation with invalid FIPS tag value2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyFIPS Mode Support with ExperimentalReleaseFeatures AFEC registered should reject an HCP cluster creation with invalid FIPS tag value2
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2077936350778101760
n/a2077891050826895360
n/a2077574106819072000
n/a2077528808046465024
expected error when creating a second external auth <external-auth> on cluster <cluster>
full failure pattern:
expected error when creating a second external auth <external-auth> on cluster <cluster>
Signal: IndeterminateSignal: Indeterminate — no prior history; active 3 day(s) — New failure pattern — no prior history
e2e420.00%4 of 20 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 3 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 0 · Jul 15: 0 · Jul 16: 0 · Jul 17: 1 · Jul 18: 2 · Jul 19: 1none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_list_and_verify.go:145]: expected error when creating a second external auth config on cluster ea-listx2qgqs
Expected
    <*fmt.wrapError | 0xc0017a0460>: 
    failed creating external auth "ea-list2" in resourcegroup="ea-list-wjf5mg" for cluster="ea-listx2qgqs": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/ea-list-wjf5mg/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/ea-listx2qgqs/externalAuths/ea-list2
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2rkumfme1e376sbr48gdhcntjdkum0hk' has already defined an external authentication"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
to match error
    <*matchers.ContainSubstringMatcher | 0xc000661770>: ...
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_list_and_verify.go:145]: expected error when creating a second external auth config on cluster ea-listx2qgqs
Expected
    <*fmt.wrapError | 0xc0017a0460>: 
    failed creating external auth "ea-list2" in resourcegroup="ea-list-wjf5mg" for cluster="ea-listx2qgqs": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/ea-list-wjf5mg/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/ea-listx2qgqs/externalAuths/ea-list2
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2rkumfme1e376sbr48gdhcntjdkum0hk' has already defined an external authentication"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
to match error
    <*matchers.ContainSubstringMatcher | 0xc000661770>: ...
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_list_and_verify.go:145]: expected error when creating a second external auth config on cluster ea-listshv2s4
Expected
    <*fmt.wrapError | 0xc0004992c0>: 
    failed creating external auth "ea-list2" in resourcegroup="ea-list-55q82h" for cluster="ea-listshv2s4": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/ea-list-55q82h/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/ea-listshv2s4/externalAuths/ea-list2
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2rks05n1ot3iotgqf52hl1ob8d6nsm7q' has already defined an external authentication"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
to match error
    <*matchers.ContainSubstringMatcher | 0xc000c55a70>: ...
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_list_and_verify.go:145]: expected error when creating a second external auth config on cluster ea-listshv2s4
Expected
    <*fmt.wrapError | 0xc0004992c0>: 
    failed creating external auth "ea-list2" in resourcegroup="ea-list-55q82h" for cluster="ea-listshv2s4": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/ea-list-55q82h/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/ea-listshv2s4/externalAuths/ea-list2
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2rks05n1ot3iotgqf52hl1ob8d6nsm7q' has already defined an external authentication"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
to match error
    <*matchers.ContainSubstringMatcher | 0xc000c55a70>: ...
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_list_and_verify.go:145]: expected error when creating a second external auth config on cluster ea-listdj8zqd
Expected
    <*fmt.wrapError | 0xc000aa45a0>: 
    failed creating external auth "ea-list2" in resourcegroup="ea-list-ptr6b8" for cluster="ea-listdj8zqd": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/ea-list-ptr6b8/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/ea-listdj8zqd/externalAuths/ea-list2
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2rk9i13nt58n3rae72l5qtsb1c6h4g8f' has already defined an external authentication"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
to match error
    <*matchers.ContainSubstringMatcher | 0xc001716d80>: ...
fail [github.com/Azure/ARO-HCP/test/e2e/external_auth_list_and_verify.go:145]: expected error when creating a second external auth config on cluster ea-listdj8zqd
Expected
    <*fmt.wrapError | 0xc000aa45a0>: 
    failed creating external auth "ea-list2" in resourcegroup="ea-list-ptr6b8" for cluster="ea-listdj8zqd": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/ea-list-ptr6b8/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/ea-listdj8zqd/externalAuths/ea-list2
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Cluster '2rk9i13nt58n3rae72l5qtsb1c6h4g8f' has already defined an external authentication"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
to match error
    <*matchers.ContainSubstringMatcher | 0xc001716d80>: ...
Contributing tests (2)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster2
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should be able to lifecycle and confirm external auth on a cluster2
Affected runs (4)
Date (UTC)Associated PRProw job
n/a2078661107169366016
n/a2078615808061214720
n/a2078298716267089920
n/a2078253416945029120
tls: failed to verify certificate: x509: certificate signed by unknown authority
full failure pattern:
tls: failed to verify certificate: x509: certificate signed by unknown authority
Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)
e2e210.00%2 of 20 job runs affectedIndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s)Show trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 1 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 0 · Jul 19: 1none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:172]: failed to verify simple web app runs on cluster "cluster-candidate-4-22-wkm784"
Unexpected error:
    <*fmt.wrapError | 0xc000e9cc60>: 
    route was never reachable: Get "https://agnhost-e2e-sample-app-pfn9f.apps.aro.c9e4m1a0i5z5t6h.kadt.uksouthstaging.aroapp-hcp.io": tls: failed to verify certificate: x509: certificate signed by unknown authority
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:172]: failed to verify simple web app runs on cluster "cluster-candidate-4-22-wkm784"
Unexpected error:
    <*fmt.wrapError | 0xc000e9cc60>: 
    route was never reachable: Get "https://agnhost-e2e-sample-app-pfn9f.apps.aro.c9e4m1a0i5z5t6h.kadt.uksouthstaging.aroapp-hcp.io": tls: failed to verify certificate: x509: certificate signed by unknown authority
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:172]: failed to verify simple web app runs on cluster "cluster-nightly-4-22-qp54cz"
Unexpected error:
    <*fmt.wrapError | 0xc000fac760>: 
    route was never reachable: Get "https://agnhost-e2e-serving-app-5tmbd.apps.aro.n8a8s5k4h5j8n9o.xdjt.uksouthstaging.aroapp-hcp.io": tls: failed to verify certificate: x509: certificate signed by unknown authority
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:172]: failed to verify simple web app runs on cluster "cluster-nightly-4-22-qp54cz"
Unexpected error:
    <*fmt.wrapError | 0xc000fac760>: 
    route was never reachable: Get "https://agnhost-e2e-serving-app-5tmbd.apps.aro.n8a8s5k4h5j8n9o.xdjt.uksouthstaging.aroapp-hcp.io": tls: failed to verify certificate: x509: certificate signed by unknown authority
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.221
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/a2078661107169366016
n/a2077166474224472064
DeleteHCPCluster timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
DeleteHCPCluster timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)
e2e15.00%1 of 20 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)Show trend detailsJul 12: 0 · Jul 13: 1 · Jul 14: 0 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:283]: Unexpected error:
    <*errors.joinError | 0xc000fd82a0>: 
    failed to cleanup resource group: failed deleting hcp clusters in resourcegroup="rg-cluster-back-version-pch5q2", caused by: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-pch5q2" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster cluster-ver-4-19 in resource group rg-cluster-back-version-pch5q2, error: context deadline exceeded, error: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-pch5q2" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster cluster-ver-4-19 in resource group rg-cluster-back-version-pch5q2, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:283]: Unexpected error:
    <*errors.joinError | 0xc000fd82a0>: 
    failed to cleanup resource group: failed deleting hcp clusters in resourcegroup="rg-cluster-back-version-pch5q2", caused by: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-pch5q2" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster cluster-ver-4-19 in resource group rg-cluster-back-version-pch5q2, error: context deadline exceeded, error: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-pch5q2" to finish deleting, caused by: timeout '25.000000' minutes exceeded during DeleteHCPCluster for cluster cluster-ver-4-19 in resource group rg-cluster-back-version-pch5q2, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster with back-level version 4.191
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2076486900469731328
ERROR CODE: InternalServerError; detail message [clusterServiceNodePoolStatus] <no_message>; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: InternalServerError; detail message [clusterServiceNodePoolStatus] <no_message>; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e15.00%1 of 20 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 0 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 1 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:190]: failed to verify nodes are Ready with Cilium CNI for cluster "cilium-cluster"
Unexpected error:
    <*errors.joinError | 0xc00131e060>: 
    VerifyNodesReady failed: no nodes found in the cluster
    VerifyCiliumOperational failed: not all pods in kube-system namespace are running: failed to list pods in kube-system namespace: client rate limiter Wait returned an error: context deadline exceeded
    failed to create NodePool cilium-np: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-gs9j2m" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/d82a69a0-d4d4-415e-af87-207e4ddcdd1b
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/d82a69a0-d4d4-415e-af87-207e4ddcdd1b",
      "name": "d82a69a0-d4d4-415e-af87-207e4ddcdd1b",
      "status": "Failed",
      "startTime": "2026-07-18T23:17:15.12448924Z",
      "endTime": "2026-07-18T23:36:15.079494126Z",
      "error": {
        "code": "InternalServerError",
        "message": "[clusterServiceNodePoolStatus] \u003cno_message\u003e"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:190]: failed to verify nodes are Ready with Cilium CNI for cluster "cilium-cluster"
Unexpected error:
    <*errors.joinError | 0xc00131e060>: 
    VerifyNodesReady failed: no nodes found in the cluster
    VerifyCiliumOperational failed: not all pods in kube-system namespace are running: failed to list pods in kube-system namespace: client rate limiter Wait returned an error: context deadline exceeded
    failed to create NodePool cilium-np: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-gs9j2m" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/d82a69a0-d4d4-415e-af87-207e4ddcdd1b
    --------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
    --------------------------------------------------------------------------------
    {
      "id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/d82a69a0-d4d4-415e-af87-207e4ddcdd1b",
      "name": "d82a69a0-d4d4-415e-af87-207e4ddcdd1b",
      "status": "Failed",
      "startTime": "2026-07-18T23:17:15.12448924Z",
      "endTime": "2026-07-18T23:36:15.079494126Z",
      "error": {
        "code": "InternalServerError",
        "message": "[clusterServiceNodePoolStatus] \u003cno_message\u003e"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer 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/a2078615808061214720
VerifyCiliumConnectivityChecks failed: failed to create test resource from artifacts/cilium-connectivity-check-1.19.2/connectivity-check-internal.0014.yaml: Service "echo-b" is in...
full failure pattern:
VerifyCiliumConnectivityChecks failed: failed to create test resource from artifacts/cilium-connectivity-check-1.19.2/connectivity-check-internal.0014.yaml: Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31414: provided port is already
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e15.00%1 of 20 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 0 · Jul 14: 0 · Jul 15: 0 · Jul 16: 0 · Jul 17: 1 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:194]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc0025febd0>: 
    VerifyCiliumConnectivityChecks failed: failed to create test resource from artifacts/cilium-connectivity-check-1.19.2/connectivity-check-internal.0014.yaml: Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31414: provided port is already allocated
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:194]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc0025febd0>: 
    VerifyCiliumConnectivityChecks failed: failed to create test resource from artifacts/cilium-connectivity-check-1.19.2/connectivity-check-internal.0014.yaml: Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31414: provided port is already allocated
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer 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/a2078253416945029120
x509: certificate signed by unknown authority
full failure pattern:
x509: certificate signed by unknown authority
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e15.00%1 of 20 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJul 12: 0 · Jul 13: 1 · Jul 14: 0 · Jul 15: 0 · Jul 16: 0 · Jul 17: 0 · Jul 18: 0 · Jul 19: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:167]: Timed out after 600.000s.
expect ingress certificate to be signed by a trusted Azure CA
Expected success, but got an error:
    <x509.UnknownAuthorityError>: 
    x509: certificate signed by unknown authority
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:167]: Timed out after 600.000s.
expect ingress certificate to be signed by a trusted Azure CA
Expected success, but got an error:
    <x509.UnknownAuthorityError>: 
    x509: certificate signed by unknown authority
    ...
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallel-ocp-nightlyCustomer should create an HCP cluster and validate TLS certificates1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2076804081216655360