No failure patterns match your search.
Environment: INT
Failure patterns: 4 · Failures matched: 19 · Total runs: 7 · Runs affected: 1
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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 | e2e | 1 | 14.29%1 of 7 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | Show trend detailsApr 25: 0 · Apr 26: 0 · Apr 27: 0 · Apr 28: 0 · Apr 29: 0 · Apr 30: 0 · May 1: 9 | none | ||||||||||||||||||||||||||||||||||||||||||||||
Full failure examples (2)fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:127]: 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:127]: 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:100]: 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:100]: 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 (9)
Affected runs (1)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
failed to get latest install version for candidate channel: query candidate graph for <ocp-channel> returned 503 Service Unavailable: upstream connect error or disconnect/reset be...full failure pattern: failed to get latest install version for candidate channel: query candidate graph for <ocp-channel> returned 503 Service Unavailable: upstream connect error or disconnect/reset before headers. reset reason: overflow Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | e2e | 1 | 14.29%1 of 7 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | Show trend detailsApr 25: 0 · Apr 26: 0 · Apr 27: 0 · Apr 28: 0 · Apr 29: 0 · Apr 30: 0 · May 1: 4 | none | ||||||||||||||||||||||||||||||||||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:100]: failed to get latest install version for candidate channel: query candidate graph for candidate-4.20 returned 503 Service Unavailable: upstream connect error or disconnect/reset before headers. reset reason: overflow fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:100]: failed to get latest install version for candidate channel: query candidate graph for candidate-4.20 returned 503 Service Unavailable: upstream connect error or disconnect/reset before headers. reset reason: overflow Contributing tests (4)
Affected runs (1)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
ResponseFailed: unexpected HTTP status: 504 Gateway Timeoutfull failure pattern: ResponseFailed: unexpected HTTP status: 504 Gateway Timeout Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | e2e | 1 | 14.29%1 of 7 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | Show trend detailsApr 25: 0 · Apr 26: 0 · Apr 27: 0 · Apr 28: 0 · Apr 29: 0 · Apr 30: 0 · May 1: 3 | none | ||||||||||||||||||||||||||||||||||||||||||||||
Full failure examples (3)fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:64]: Unexpected error:
<*cincinnati.Error | 0xc001000000>:
ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:64]: Unexpected error:
<*cincinnati.Error | 0xc001000000>:
ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
...
occurredfail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:76]: Unexpected error:
<*cincinnati.Error | 0xc000ee3620>:
ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:76]: Unexpected error:
<*cincinnati.Error | 0xc000ee3620>:
ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
...
occurredfail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:64]: Unexpected error:
<*cincinnati.Error | 0xc000e00000>:
ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:64]: Unexpected error:
<*cincinnati.Error | 0xc000e00000>:
ResponseFailed: unexpected HTTP status: 504 Gateway Timeout
...
occurredContributing tests (3)
Affected runs (1)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
failed to get latest install version for candidate channel: query candidate graph for <ocp-channel> returned 503 Service Unavailable: <html>full failure pattern: failed to get latest install version for candidate channel: 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 | e2e | 1 | 14.29%1 of 7 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | Show trend detailsApr 25: 0 · Apr 26: 0 · Apr 27: 0 · Apr 28: 0 · Apr 29: 0 · Apr 30: 0 · May 1: 3 | none | ||||||||||||||||||||||||||||||||||||||||||||||
Full failure examples (2)fail [github.com/Azure/ARO-HCP/test/util/framework/deployment_params.go:100]: failed to get latest install version for candidate channel: 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:100]: failed to get latest install version for candidate channel: 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:127]: failed to get latest install version for candidate channel: 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:127]: failed to get latest install version for candidate channel: 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)
Affected runs (1)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||