<
Single Day: Jul 6
> Reset
View JSON API

Environment: STG

Failure patterns: 8 · Failures matched: 38 · Total runs: 4 · Runs affected: 4

Failure patternThe canonical description of a recurring CI failure, extracted and normalized from raw logs.Failed atThe stage of the job run where this failure occurred: 'provision' (environment setup, DEV only), 'e2e' (test suite execution), or 'other' (CI infrastructure issues that did not produce a failure pattern).Number of distinct job runs where this failure pattern was detected.Percentage of all job runs in this environment affected by this failure pattern during the selected window.Classification of this failure pattern: Regression (likely caused by a specific PR), Flake (intermittent failure spread across days), Noise (low-quality or generic pattern), or Indeterminate.TrendShows daily activity for this failure pattern in a trailing window anchored to the selected end date. The sparkline covers at least 7 days and at most 14 days, depending on the current window size.Also inOther environments where the same failure pattern was also detected during the selected window.
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)
e2e4100.00%4 of 4 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJun 30: 0 · Jul 1: 0 · Jul 2: 0 · Jul 3: 0 · Jul 4: 0 · Jul 5: 0 · Jul 6: 13none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:159]: failed to create node pool "np-rw5292" for cluster "cluster-nightly-4-20-rw5292"
Unexpected error:
    <*fmt.wrapErrors | 0xc00251f860>: 
    failed to create NodePool np-rw5292, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-rw5292 in resource group rg-nightly-4-20-g8lx9j, error: failed waiting for nodepool="np-rw5292" for cluster "cluster-nightly-4-20-rw5292" in resourcegroup="rg-nightly-4-20-g8lx9j" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:159]: failed to create node pool "np-rw5292" for cluster "cluster-nightly-4-20-rw5292"
Unexpected error:
    <*fmt.wrapErrors | 0xc00251f860>: 
    failed to create NodePool np-rw5292, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-rw5292 in resource group rg-nightly-4-20-g8lx9j, error: failed waiting for nodepool="np-rw5292" for cluster "cluster-nightly-4-20-rw5292" in resourcegroup="rg-nightly-4-20-g8lx9j" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:136]: failed to create node pool "np-1" for private keyvault cluster "private-kv-cluster"
Unexpected error:
    <*fmt.wrapErrors | 0xc002a91530>: 
    failed to create NodePool np-1, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-lxfx2v, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-lxfx2v" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:136]: failed to create node pool "np-1" for private keyvault cluster "private-kv-cluster"
Unexpected error:
    <*fmt.wrapErrors | 0xc002a91530>: 
    failed to create NodePool np-1, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-lxfx2v, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-lxfx2v" to finish creating: context deadline exceeded
    ...
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 | 0xc0017a2468>: 
    VerifyNodesReady failed: no nodes found in the cluster
    VerifyCiliumOperational failed: not all pods in kube-system namespace are running: no cilium pods found in kube-system namespace
    failed to create NodePool cilium-np, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool cilium-np in resource group complex-cilium-kv-r77729, error: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-r77729" to finish creating: context deadline exceeded
    ...
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 | 0xc0017a2468>: 
    VerifyNodesReady failed: no nodes found in the cluster
    VerifyCiliumOperational failed: not all pods in kube-system namespace are running: no cilium pods found in kube-system namespace
    failed to create NodePool cilium-np, caused by: timeout '20.000000' minutes exceeded during CreateNodePoolFromParam for node pool cilium-np in resource group complex-cilium-kv-r77729, error: failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="complex-cilium-kv-r77729" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (11)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API2
e2ebranch-ci-Azure-ARO-HCP-main-e2e-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
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.201
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.201
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
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
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 successfully1
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 tag1
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.201
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 API1
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 (4)
Date (UTC)Associated PRProw job
n/a2074267232510152704
n/a2074102247611961344
n/a2074027709368897536
n/a2073950128116338688
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)
e2e375.00%3 of 4 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsJun 30: 0 · Jul 1: 0 · Jul 2: 0 · Jul 3: 0 · Jul 4: 0 · Jul 5: 0 · Jul 6: 4none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-nightly-4-23-g897nm/cluster-nightly-4-23-gjksrw should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc001076ae0>: 
    failed to create HCP cluster cluster-nightly-4-23-gjksrw, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-4-23-gjksrw in resource group rg-nightly-4-23-g897nm, error: failed waiting for cluster="cluster-nightly-4-23-gjksrw" in resourcegroup="rg-nightly-4-23-g897nm" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-4-23-gjksrw in resource group rg-nightly-4-23-g897nm, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-nightly-4-23-g897nm/cluster-nightly-4-23-gjksrw should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc001076ae0>: 
    failed to create HCP cluster cluster-nightly-4-23-gjksrw, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-4-23-gjksrw in resource group rg-nightly-4-23-g897nm, error: failed waiting for cluster="cluster-nightly-4-23-gjksrw" in resourcegroup="rg-nightly-4-23-g897nm" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-4-23-gjksrw in resource group rg-nightly-4-23-g897nm, 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-5ghdp7/cluster-nightly-5-0-r2rdcg should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000909e90>: 
    failed to create HCP cluster cluster-nightly-5-0-r2rdcg, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-r2rdcg in resource group rg-nightly-5-0-5ghdp7, error: failed waiting for cluster="cluster-nightly-5-0-r2rdcg" in resourcegroup="rg-nightly-5-0-5ghdp7" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-r2rdcg in resource group rg-nightly-5-0-5ghdp7, 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-5ghdp7/cluster-nightly-5-0-r2rdcg should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000909e90>: 
    failed to create HCP cluster cluster-nightly-5-0-r2rdcg, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-r2rdcg in resource group rg-nightly-5-0-5ghdp7, error: failed waiting for cluster="cluster-nightly-5-0-r2rdcg" in resourcegroup="rg-nightly-5-0-5ghdp7" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-nightly-5-0-r2rdcg in resource group rg-nightly-5-0-5ghdp7, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-5-0-wg275n/cluster-candidate-5-0-tcf7s2 should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc00179bc50>: 
    failed to create HCP cluster cluster-candidate-5-0-tcf7s2, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-tcf7s2 in resource group rg-candidate-5-0-wg275n, error: failed waiting for cluster="cluster-candidate-5-0-tcf7s2" in resourcegroup="rg-candidate-5-0-wg275n" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-tcf7s2 in resource group rg-candidate-5-0-wg275n, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:106]: HCP cluster rg-candidate-5-0-wg275n/cluster-candidate-5-0-tcf7s2 should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc00179bc50>: 
    failed to create HCP cluster cluster-candidate-5-0-tcf7s2, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-tcf7s2 in resource group rg-candidate-5-0-wg275n, error: failed waiting for cluster="cluster-candidate-5-0-tcf7s2" in resourcegroup="rg-candidate-5-0-wg275n" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223FromParam for cluster cluster-candidate-5-0-tcf7s2 in resource group rg-candidate-5-0-wg275n, error: context deadline exceeded
    ...
occurred
Contributing tests (4)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-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-stage-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-stage-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-stage-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/a2074267232510152704
n/a2074102247611961344
n/a2073950128116338688
failed to get latest install version for candidate channel: query candidate graph for <ocp-channel>: Get "<url>": context deadline exceeded (Client.Timeout exceeded while awaiting...
full failure pattern:
failed to get latest install version for candidate channel: query candidate graph for <ocp-channel>: Get "<url>": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 30: 0 · Jul 1: 0 · Jul 2: 0 · Jul 3: 0 · Jul 4: 0 · Jul 5: 0 · Jul 6: 10none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:179]: failed to get latest install version for candidate channel: query candidate graph for candidate-4.20: Get "https://api.openshift.com/api/upgrades_info/v1/graph?channel=candidate-4.20": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:179]: failed to get latest install version for candidate channel: query candidate graph for candidate-4.20: Get "https://api.openshift.com/api/upgrades_info/v1/graph?channel=candidate-4.20": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Contributing tests (10)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create a cluster with an external auth config and get the external auth config1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled up to replica limits1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create an HCP cluster and manage ImageDigestMirrors1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to forward control plane logs to a storage account and Event Hub via shoebox diagnostic settings1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should not be able to perform various invalid operations on cluster resources1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should respect cluster-wide node limits with nodepool autoscaling1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelNodepool Ephemeral OS Disk should create a nodepool with ephemeral OS disk when autoRepair is enabled1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.191
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.211
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.221
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2074027709368897536
after 4 attempts: ResponseFailed: unexpected HTTP status: 503 Service Unavailable
full failure pattern:
after 4 attempts: ResponseFailed: unexpected HTTP status: 503 Service Unavailable
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 30: 0 · Jul 1: 0 · Jul 2: 0 · Jul 3: 0 · Jul 4: 0 · Jul 5: 0 · Jul 6: 4none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:65]: failed to determine z-stream install version for minor 4.21
Unexpected error:
    <*fmt.wrapError | 0xc000d62860>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 503 Service Unavailable
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:65]: failed to determine z-stream install version for minor 4.21
Unexpected error:
    <*fmt.wrapError | 0xc000d62860>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 503 Service Unavailable
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:400]: failed to get latest version for nodepool minor 4.20
Unexpected error:
    <*fmt.wrapError | 0xc0008085c0>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 503 Service Unavailable
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:400]: failed to get latest version for nodepool minor 4.20
Unexpected error:
    <*fmt.wrapError | 0xc0008085c0>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 503 Service Unavailable
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:536]: failed to get versions for minor 4.21
Unexpected error:
    <*fmt.wrapError | 0xc000e1c460>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 503 Service Unavailable
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:536]: failed to get versions for minor 4.21
Unexpected error:
    <*fmt.wrapError | 0xc000e1c460>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 503 Service Unavailable
    ...
occurred
Contributing tests (4)
Failed AtJobTestSupport
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
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.21.zLatest1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should upgrade and update a nodepool from 4.21.z to 4.21.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2074027709368897536
failed to get latest install version for candidate channel: after 4 attempts: query candidate graph for <ocp-channel> returned 503 Service Unavailable: <html>
full failure pattern:
failed to get latest install version for candidate channel: after 4 attempts: query candidate graph for <ocp-channel> returned 503 Service Unavailable: <html>
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 30: 0 · Jul 1: 0 · Jul 2: 0 · Jul 3: 0 · Jul 4: 0 · Jul 5: 0 · Jul 6: 3none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:179]: failed to get latest install version for candidate channel: after 4 attempts: query candidate graph for candidate-4.20 returned 503 Service Unavailable: <html>
  <head>
    <meta name="viewport" content="width=device-width, initial-scale=1">

    <style type="text/css">
      body {
        font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
        line-height: 1.66666667;
        font-size: 16px;
        color: #333;
        background-color: #fff;
        margin: 2em 1em;
      }
      h1 {
        font-size: 28px;
        font-weight: 400;
      }
      p {
        margin: 0 0 10px;
      }
      .alert.alert-info {
        background-color: #F0F0F0;
        margin-top: 30px;
        padding: 30px;
      }
      .alert p {
        padding-left: 35px;
      }
      ul {
        padding-left: 51px;
        position: relative;
      }
      li {
        font-size: 14px;
        margin-bottom: 1em;
      }
      p.info {
        position: relative;
        font-size: 20px;
      }
      p.info:before, p.info:after {
        content: "";
        left: 0;
        position: absolute;
        top: 0;
      }
      p.info:before {
        background: #0066CC;
        border-radius: 16px;
        color: #fff;
        content: "i";
        font: bold 16px/24px serif;
        height: 24px;
        left: 0px;
        text-align: center;
        top: 4px;
        width: 24px;
      }

      @media (min-width: 768px) {
        body {
          margin: 6em;
        }
      }
    </style>
  </head>
  <body>
    <div>
      <h1>Application is not available</h1>
      <p>The application is currently not serving requests at this endpoint. It may not have been started or is still starting.</p>

      <div class="alert alert-info">
        <p class="info">
          Possible reasons you are seeing this page:
        </p>
        <ul>
          <li>
            <strong>The host doesn't exist.</strong>
            Make sure the hostname was typed correctly and that a route matching this hostname exists.
          </li>
          <li>
            <strong>The host exists, but doesn't have a matching path.</strong>
            Check if the URL path was typed correctly and that the route was created using the desired path.
          </li>
          <li>
            <strong>Route and path matches, but all pods are down.</strong>
            Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.
          </li>
        </ul>
      </div>
    </div>
  </body>
</html>
fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:179]: failed to get latest install version for candidate channel: after 4 attempts: query candidate graph for candidate-4.20 returned 503 Service Unavailable: <html>
  <head>
    <meta name="viewport" content="width=device-width, initial-scale=1">

    <style type="text/css">
      body {
        font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
        line-height: 1.66666667;
        font-size: 16px;
        color: #333;
        background-color: #fff;
        margin: 2em 1em;
      }
      h1 {
        font-size: 28px;
        font-weight: 400;
      }
      p {
        margin: 0 0 10px;
      }
      .alert.alert-info {
        background-color: #F0F0F0;
        margin-top: 30px;
        padding: 30px;
      }
      .alert p {
        padding-left: 35px;
      }
      ul {
        padding-left: 51px;
        position: relative;
      }
      li {
        font-size: 14px;
        margin-bottom: 1em;
      }
      p.info {
        position: relative;
        font-size: 20px;
      }
      p.info:before, p.info:after {
        content: "";
        left: 0;
        position: absolute;
        top: 0;
      }
      p.info:before {
        background: #0066CC;
        border-radius: 16px;
        color: #fff;
        content: "i";
        font: bold 16px/24px serif;
        height: 24px;
        left: 0px;
        text-align: center;
        top: 4px;
        width: 24px;
      }

      @media (min-width: 768px) {
        body {
          margin: 6em;
        }
      }
    </style>
  </head>
  <body>
    <div>
      <h1>Application is not available</h1>
      <p>The application is currently not serving requests at this endpoint. It may not have been started or is still starting.</p>

      <div class="alert alert-info">
        <p class="info">
          Possible reasons you are seeing this page:
        </p>
        <ul>
          <li>
            <strong>The host doesn't exist.</strong>
            Make sure the hostname was typed correctly and that a route matching this hostname exists.
          </li>
          <li>
            <strong>The host exists, but doesn't have a matching path.</strong>
            Check if the URL path was typed correctly and that the route was created using the desired path.
          </li>
          <li>
            <strong>Route and path matches, but all pods are down.</strong>
            Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.
          </li>
        </ul>
      </div>
    </div>
  </body>
</html>
Contributing tests (3)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create an HCP cluster with Image Registry not present1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to lifecycle and confirm external auth on a cluster1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.201
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2074027709368897536
after 4 attempts: ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
full failure pattern:
after 4 attempts: ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 30: 0 · Jul 1: 0 · Jul 2: 0 · Jul 3: 0 · Jul 4: 0 · Jul 5: 0 · Jul 6: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:677]: failed to get latest version for minor 4.21
Unexpected error:
    <*fmt.wrapError | 0xc0010be160>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:677]: failed to get latest version for minor 4.21
Unexpected error:
    <*fmt.wrapError | 0xc0010be160>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:65]: failed to determine z-stream install version for minor 4.20
Unexpected error:
    <*fmt.wrapError | 0xc000c2e120>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:65]: failed to determine z-stream install version for minor 4.20
Unexpected error:
    <*fmt.wrapError | 0xc000c2e120>: 
    after 4 attempts: ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
    ...
occurred
Contributing tests (2)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should downgrade a nodepool to a lower minor version from 4.21.zLatest to 4.19.zLatest1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.20.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2074027709368897536
failed to get latest install version for candidate channel: after 4 attempts: query candidate graph for <ocp-channel> returned 504 Gateway Timeout: upstream request timeout
full failure pattern:
failed to get latest install version for candidate channel: after 4 attempts: query candidate graph for <ocp-channel> returned 504 Gateway Timeout: upstream request timeout
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 30: 0 · Jul 1: 0 · Jul 2: 0 · Jul 3: 0 · Jul 4: 0 · Jul 5: 0 · Jul 6: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:179]: failed to get latest install version for candidate channel: after 4 attempts: query candidate graph for candidate-4.20 returned 504 Gateway Timeout: upstream request timeout
fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:179]: failed to get latest install version for candidate channel: after 4 attempts: query candidate graph for candidate-4.20 returned 504 Gateway Timeout: upstream request timeout
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to use workload identity via the cluster OIDC issuer URL1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2074027709368897536
query graph for <ocp-channel>: Get "<url>": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
full failure pattern:
query graph for <ocp-channel>: Get "<url>": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e125.00%1 of 4 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsJun 30: 0 · Jul 1: 0 · Jul 2: 0 · Jul 3: 0 · Jul 4: 0 · Jul 5: 0 · Jul 6: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:257]: failed to get version pair without upgrade edge for minor 4.20
Unexpected error:
    <*fmt.wrapError | 0xc00110cee0>: 
    query graph for candidate-4.20: Get "https://api.openshift.com/api/upgrades_info/v1/graph?channel=candidate-4.20": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:257]: failed to get version pair without upgrade edge for minor 4.20
Unexpected error:
    <*fmt.wrapError | 0xc00110cee0>: 
    query graph for candidate-4.20: Get "https://api.openshift.com/api/upgrades_info/v1/graph?channel=candidate-4.20": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should upgrade a nodepool to a version without Cincinnati upgrade edge z-stream upgrade without Cincinnati edge in 4.201
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2074027709368897536