No failure patterns match your search.
Environment: STG
Failure patterns: 2 · Failures matched: 2 · Total runs: 1 · 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. | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ERROR CODE: InvalidRequestContent; detail message Cluster '<id>' is in state 'pending_update', can't update; provider Microsoft.RedHatOpenShiftfull failure pattern: ERROR CODE: InvalidRequestContent; detail message Cluster '<id>' is in state 'pending_update', can't update; provider Microsoft.RedHatOpenShift Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | e2e | 1 | 100.00%1 of 1 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | Show trend detailsApr 13: 0 · Apr 14: 0 · Apr 15: 0 · Apr 16: 0 · Apr 17: 0 · Apr 18: 0 · Apr 19: 1 | none | ||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/idms_lifecycle.go:231]: Unexpected error:
<*exported.ResponseError | 0xc001372540>:
PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/idms-bpglms/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/idms-e2e-hcp-cluster
--------------------------------------------------------------------------------
RESPONSE 400: 400 Bad Request
ERROR CODE: InvalidRequestContent
--------------------------------------------------------------------------------
{
"error": {
"code": "InvalidRequestContent",
"message": "Cluster '2pouj433hbtcf1grn5ou3pfbv6ndre84' is in state 'pending_update', can't update"
}
}
--------------------------------------------------------------------------------
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/idms_lifecycle.go:231]: Unexpected error:
<*exported.ResponseError | 0xc001372540>:
PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/idms-bpglms/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/idms-e2e-hcp-cluster
--------------------------------------------------------------------------------
RESPONSE 400: 400 Bad Request
ERROR CODE: InvalidRequestContent
--------------------------------------------------------------------------------
{
"error": {
"code": "InvalidRequestContent",
"message": "Cluster '2pouj433hbtcf1grn5ou3pfbv6ndre84' is in state 'pending_update', can't update"
}
}
--------------------------------------------------------------------------------
...
occurredContributing tests (1)
Affected runs (1)
| ||||||||||||||||||||
timeout during CreateHCPClusterAndWait; context deadline exceededfull failure pattern: timeout during CreateHCPClusterAndWait; context deadline exceeded Signal: IndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s) | e2e | 1 | 100.00%1 of 1 job runs affected | IndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s) | Show trend detailsApr 13: 0 · Apr 14: 0 · Apr 15: 0 · Apr 16: 0 · Apr 17: 0 · Apr 18: 0 · Apr 19: 1 | none | ||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:126]: Unexpected error:
<*fmt.wrapErrors | 0xc0015522a0>:
failed to create HCP cluster cp-ystream-upgrade-4-21-wk9kt6, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-21-wk9kt6 in resource group rg-cp-ystream-upgrade-4-21-fc7wft, error: failed waiting for cluster="cp-ystream-upgrade-4-21-wk9kt6" in resourcegroup="rg-cp-ystream-upgrade-4-21-fc7wft" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-21-wk9kt6 in resource group rg-cp-ystream-upgrade-4-21-fc7wft, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:126]: Unexpected error:
<*fmt.wrapErrors | 0xc0015522a0>:
failed to create HCP cluster cp-ystream-upgrade-4-21-wk9kt6, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-21-wk9kt6 in resource group rg-cp-ystream-upgrade-4-21-fc7wft, error: failed waiting for cluster="cp-ystream-upgrade-4-21-wk9kt6" in resourcegroup="rg-cp-ystream-upgrade-4-21-fc7wft" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-21-wk9kt6 in resource group rg-cp-ystream-upgrade-4-21-fc7wft, error: context deadline exceeded
...
occurredContributing tests (1)
Affected runs (1)
| ||||||||||||||||||||