No failure patterns match your search.
Environment: STG
Failure patterns: 3 · Failures matched: 3 · Total runs: 2 · Runs affected: 2
| 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. | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ERROR CODE: InternalServerError; detail message [hypershiftHostedCluster] hosted cluster has no installed version; hosted cluster degraded: UnavailableReplicas: [router]; provider...full failure pattern: ERROR CODE: InternalServerError; detail message [hypershiftHostedCluster] hosted cluster has no installed version; hosted cluster degraded: UnavailableReplicas: [router]; provider Microsoft.RedHatOpenShift Signal: IndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior history | e2e | 1 | 50.00%1 of 2 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior history | Show trend detailsJul 19: 0 · Jul 20: 0 · Jul 21: 1 · Jul 22: 0 · Jul 23: 0 · Jul 24: 0 · Jul 25: 1 | none | ||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:120]: HCP cluster rg-nightly-4-23-bxb82trtk28r/cluster-nightly-4-23-f626bt should provision
Unexpected error:
<*fmt.wrapError | 0xc000a9c1a0>:
failed to create HCP cluster cluster-nightly-4-23-f626bt: failed waiting for cluster="cluster-nightly-4-23-f626bt" in resourcegroup="rg-nightly-4-23-bxb82trtk28r" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/0f19b0d2-34e7-42c9-99c1-fa33aeb87a0d
--------------------------------------------------------------------------------
RESPONSE 200: 200 OK
ERROR CODE: InternalServerError
--------------------------------------------------------------------------------
{
"id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/0f19b0d2-34e7-42c9-99c1-fa33aeb87a0d",
"name": "0f19b0d2-34e7-42c9-99c1-fa33aeb87a0d",
"status": "Failed",
"startTime": "2026-07-25T23:02:57.404100166Z",
"endTime": "2026-07-25T23:22:19.985017273Z",
"error": {
"code": "InternalServerError",
"message": "[hypershiftHostedCluster] hosted cluster has no installed version; hosted cluster degraded: UnavailableReplicas: router deployment has 1 unavailable replicas"
}
}
--------------------------------------------------------------------------------
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:120]: HCP cluster rg-nightly-4-23-bxb82trtk28r/cluster-nightly-4-23-f626bt should provision
Unexpected error:
<*fmt.wrapError | 0xc000a9c1a0>:
failed to create HCP cluster cluster-nightly-4-23-f626bt: failed waiting for cluster="cluster-nightly-4-23-f626bt" in resourcegroup="rg-nightly-4-23-bxb82trtk28r" to finish creating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/0f19b0d2-34e7-42c9-99c1-fa33aeb87a0d
--------------------------------------------------------------------------------
RESPONSE 200: 200 OK
ERROR CODE: InternalServerError
--------------------------------------------------------------------------------
{
"id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/0f19b0d2-34e7-42c9-99c1-fa33aeb87a0d",
"name": "0f19b0d2-34e7-42c9-99c1-fa33aeb87a0d",
"status": "Failed",
"startTime": "2026-07-25T23:02:57.404100166Z",
"endTime": "2026-07-25T23:22:19.985017273Z",
"error": {
"code": "InternalServerError",
"message": "[hypershiftHostedCluster] hosted cluster has no installed version; hosted cluster degraded: UnavailableReplicas: router deployment has 1 unavailable replicas"
}
}
--------------------------------------------------------------------------------
...
occurredContributing tests (1)
Affected runs (1)
| ||||||||||||||||||||
x509: certificate signed by unknown authorityfull failure pattern: x509: certificate signed by unknown authority Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s) | e2e | 1 | 50.00%1 of 2 job runs affected | IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s) | Show trend detailsJul 19: 0 · Jul 20: 0 · Jul 21: 0 · Jul 22: 0 · Jul 23: 0 · Jul 24: 0 · Jul 25: 1 | none | ||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:234]: Timed out after 600.002s.
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:234]: Timed out after 600.002s.
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)
Affected runs (1)
| ||||||||||||||||||||
DeleteHCPCluster timed out after <minutes> minutes; context deadline exceededfull failure pattern: DeleteHCPCluster timed out after <minutes> minutes; context deadline exceeded Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 1 day(s) | e2e | 1 | 50.00%1 of 2 job runs affected | IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 1 day(s) | Show trend detailsJul 19: 0 · Jul 20: 0 · Jul 21: 0 · Jul 22: 0 · Jul 23: 0 · Jul 24: 0 · Jul 25: 1 | none | ||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:285]: Unexpected error:
<*errors.joinError | 0xc00123e2b8>:
failed to cleanup resource group: failed deleting hcp clusters in resourcegroup="rg-cluster-back-version-z4fpldkzrbd9", caused by: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-z4fpldkzrbd9" 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-z4fpldkzrbd9, error: context deadline exceeded, error: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-z4fpldkzrbd9" 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-z4fpldkzrbd9, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:285]: Unexpected error:
<*errors.joinError | 0xc00123e2b8>:
failed to cleanup resource group: failed deleting hcp clusters in resourcegroup="rg-cluster-back-version-z4fpldkzrbd9", caused by: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-z4fpldkzrbd9" 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-z4fpldkzrbd9, error: context deadline exceeded, error: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-z4fpldkzrbd9" 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-z4fpldkzrbd9, error: context deadline exceeded
...
occurredContributing tests (1)
Affected runs (1)
| ||||||||||||||||||||