No failure patterns match your search.
Environment: INT
Failure patterns: 6 · Failures matched: 18 · Total runs: 6 · Runs affected: 6
| 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 timed out after 29s waiting for resolution of desired version from '4.21.15' cluster version; provider Microsoft.RedHatOpenShiftfull failure pattern: ERROR CODE: InvalidRequestContent; detail message timed out after 29s waiting for resolution of desired version from '4.21.15' cluster version; provider Microsoft.RedHatOpenShift Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | e2e | 6 | 100.00%6 of 6 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | Show trend detailsMay 7: 0 · May 8: 0 · May 9: 0 · May 10: 0 · May 11: 0 · May 12: 0 · May 13: 6 | none | |||||||||||||||||||||||||||||||||||||||||
Full failure examples (3)fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:160]: Unexpected error:
<*fmt.wrapError | 0xc0008449c0>:
failed waiting for hcpCluster="cp-ystream-upgrade-4-21-x9glvp" in resourcegroup="rg-cp-ystream-upgrade-4-21-k7tb76" to finish updating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/82580c93-80ca-4782-a780-8beefa3ca171
--------------------------------------------------------------------------------
RESPONSE 200: 200 OK
ERROR CODE: InvalidRequestContent
--------------------------------------------------------------------------------
{
"id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/82580c93-80ca-4782-a780-8beefa3ca171",
"name": "82580c93-80ca-4782-a780-8beefa3ca171",
"status": "Failed",
"startTime": "2026-05-14T00:41:19.022062955Z",
"endTime": "2026-05-14T00:42:47.115197921Z",
"error": {
"code": "InvalidRequestContent",
"message": "timed out after 29s waiting for resolution of desired version from '4.21.15' cluster version"
}
}
--------------------------------------------------------------------------------
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:160]: Unexpected error:
<*fmt.wrapError | 0xc0008449c0>:
failed waiting for hcpCluster="cp-ystream-upgrade-4-21-x9glvp" in resourcegroup="rg-cp-ystream-upgrade-4-21-k7tb76" to finish updating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/82580c93-80ca-4782-a780-8beefa3ca171
--------------------------------------------------------------------------------
RESPONSE 200: 200 OK
ERROR CODE: InvalidRequestContent
--------------------------------------------------------------------------------
{
"id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/82580c93-80ca-4782-a780-8beefa3ca171",
"name": "82580c93-80ca-4782-a780-8beefa3ca171",
"status": "Failed",
"startTime": "2026-05-14T00:41:19.022062955Z",
"endTime": "2026-05-14T00:42:47.115197921Z",
"error": {
"code": "InvalidRequestContent",
"message": "timed out after 29s waiting for resolution of desired version from '4.21.15' cluster version"
}
}
--------------------------------------------------------------------------------
...
occurredfail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:160]: Unexpected error:
<*fmt.wrapError | 0xc000c94560>:
failed waiting for hcpCluster="cp-ystream-upgrade-4-21-gjf5t9" in resourcegroup="rg-cp-ystream-upgrade-4-21-fg6lv9" to finish updating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/5f247cdd-5812-4761-b99d-f988d2cb1453
--------------------------------------------------------------------------------
RESPONSE 200: 200 OK
ERROR CODE: InvalidRequestContent
--------------------------------------------------------------------------------
{
"id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/5f247cdd-5812-4761-b99d-f988d2cb1453",
"name": "5f247cdd-5812-4761-b99d-f988d2cb1453",
"status": "Failed",
"startTime": "2026-05-13T21:07:58.388882897Z",
"endTime": "2026-05-13T21:09:22.905598885Z",
"error": {
"code": "InvalidRequestContent",
"message": "timed out after 29s waiting for resolution of desired version from '4.21.15' cluster version"
}
}
--------------------------------------------------------------------------------
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:160]: Unexpected error:
<*fmt.wrapError | 0xc000c94560>:
failed waiting for hcpCluster="cp-ystream-upgrade-4-21-gjf5t9" in resourcegroup="rg-cp-ystream-upgrade-4-21-fg6lv9" to finish updating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/5f247cdd-5812-4761-b99d-f988d2cb1453
--------------------------------------------------------------------------------
RESPONSE 200: 200 OK
ERROR CODE: InvalidRequestContent
--------------------------------------------------------------------------------
{
"id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/5f247cdd-5812-4761-b99d-f988d2cb1453",
"name": "5f247cdd-5812-4761-b99d-f988d2cb1453",
"status": "Failed",
"startTime": "2026-05-13T21:07:58.388882897Z",
"endTime": "2026-05-13T21:09:22.905598885Z",
"error": {
"code": "InvalidRequestContent",
"message": "timed out after 29s waiting for resolution of desired version from '4.21.15' cluster version"
}
}
--------------------------------------------------------------------------------
...
occurredfail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:160]: Unexpected error:
<*fmt.wrapError | 0xc000dac400>:
failed waiting for hcpCluster="cp-ystream-upgrade-4-21-mtqjkn" in resourcegroup="rg-cp-ystream-upgrade-4-21-n4zbgv" to finish updating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/182072e0-9b74-4cef-b677-89a453c15273
--------------------------------------------------------------------------------
RESPONSE 200: 200 OK
ERROR CODE: InvalidRequestContent
--------------------------------------------------------------------------------
{
"id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/182072e0-9b74-4cef-b677-89a453c15273",
"name": "182072e0-9b74-4cef-b677-89a453c15273",
"status": "Failed",
"startTime": "2026-05-13T16:20:21.870546037Z",
"endTime": "2026-05-13T16:22:13.927370791Z",
"error": {
"code": "InvalidRequestContent",
"message": "timed out after 29s waiting for resolution of desired version from '4.21.15' cluster version"
}
}
--------------------------------------------------------------------------------
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:160]: Unexpected error:
<*fmt.wrapError | 0xc000dac400>:
failed waiting for hcpCluster="cp-ystream-upgrade-4-21-mtqjkn" in resourcegroup="rg-cp-ystream-upgrade-4-21-n4zbgv" to finish updating: GET https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/182072e0-9b74-4cef-b677-89a453c15273
--------------------------------------------------------------------------------
RESPONSE 200: 200 OK
ERROR CODE: InvalidRequestContent
--------------------------------------------------------------------------------
{
"id": "/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.RedHatOpenShift/locations/uksouth/hcpOperationStatuses/182072e0-9b74-4cef-b677-89a453c15273",
"name": "182072e0-9b74-4cef-b677-89a453c15273",
"status": "Failed",
"startTime": "2026-05-13T16:20:21.870546037Z",
"endTime": "2026-05-13T16:22:13.927370791Z",
"error": {
"code": "InvalidRequestContent",
"message": "timed out after 29s waiting for resolution of desired version from '4.21.15' cluster version"
}
}
--------------------------------------------------------------------------------
...
occurredContributing tests (1)
Affected runs (6)
| |||||||||||||||||||||||||||||||||||||||||||||||
failed to cleanup resource group: at least one HCP cluster <cluster> to delete: failed waiting for hcpcluster="<cluster>" in resourcegroup="<resource-group>" to finish deleting: c...full failure pattern: failed to cleanup resource group: at least one HCP cluster <cluster> to delete: failed waiting for hcpcluster="<cluster>" in resourcegroup="<resource-group>" to finish deleting: context canceled Signal: IndeterminateSignal: Indeterminate — no prior history; active 3 day(s) — New failure pattern — no prior history | e2e | 2 | 33.33%2 of 6 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 3 day(s) — New failure pattern — no prior history | Show trend detailsMay 7: 0 · May 8: 0 · May 9: 0 · May 10: 0 · May 11: 1 · May 12: 10 · May 13: 7 | none | |||||||||||||||||||||||||||||||||||||||||
Full failure examples (3)fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
<*errors.joinError | 0xc001312198>:
failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="admin-cred-lifecycle-9mdxlx" in resourcegroup="admin-credential-lifecycle-test-5szj8p" to finish deleting: context canceled
...
occurred
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
<*errors.joinError | 0xc001312198>:
failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="admin-cred-lifecycle-9mdxlx" in resourcegroup="admin-credential-lifecycle-test-5szj8p" to finish deleting: context canceled
...
occurred
fail [:0]: A node timeout occurredfail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
<*errors.joinError | 0xc000df61e0>:
failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-hgw8jz" to finish deleting: context canceled
...
occurred
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
<*errors.joinError | 0xc000df61e0>:
failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-hgw8jz" to finish deleting: context canceled
...
occurred
fail [:0]: A node timeout occurredfail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
<*errors.joinError | 0xc001726438>:
failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="pullsecret-hcp-cluster" in resourcegroup="pullsecret-test-whxwt2" to finish deleting: context canceled
...
occurred
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
<*errors.joinError | 0xc001726438>:
failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="pullsecret-hcp-cluster" in resourcegroup="pullsecret-test-whxwt2" to finish deleting: context canceled
...
occurred
fail [:0]: A node timeout occurredContributing tests (7)
Affected runs (2)
| |||||||||||||||||||||||||||||||||||||||||||||||
timeout during CreateHCPClusterAndWait; context deadline exceededfull failure pattern: timeout during CreateHCPClusterAndWait; context deadline exceeded Signal: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s) | e2e | 2 | 33.33%2 of 6 job runs affected | IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s) | Show trend detailsMay 7: 0 · May 8: 0 · May 9: 0 · May 10: 0 · May 11: 0 · May 12: 0 · May 13: 2 | none | |||||||||||||||||||||||||||||||||||||||||
Full failure examples (2)fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:130]: Unexpected error:
<*fmt.wrapErrors | 0xc00136ec60>:
failed to create HCP cluster np-version-upgrade-cluster-98czdp, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-version-upgrade-cluster-98czdp in resource group rg-np-version-upgrade-98czdp-6t5bts, error: failed waiting for cluster="np-version-upgrade-cluster-98czdp" in resourcegroup="rg-np-version-upgrade-98czdp-6t5bts" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-version-upgrade-cluster-98czdp in resource group rg-np-version-upgrade-98czdp-6t5bts, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:130]: Unexpected error:
<*fmt.wrapErrors | 0xc00136ec60>:
failed to create HCP cluster np-version-upgrade-cluster-98czdp, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-version-upgrade-cluster-98czdp in resource group rg-np-version-upgrade-98czdp-6t5bts, error: failed waiting for cluster="np-version-upgrade-cluster-98czdp" in resourcegroup="rg-np-version-upgrade-98czdp-6t5bts" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster np-version-upgrade-cluster-98czdp in resource group rg-np-version-upgrade-98czdp-6t5bts, error: context deadline exceeded
...
occurredfail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:141]: Unexpected error:
<*fmt.wrapErrors | 0xc0014b4ff0>:
failed to create HCP cluster cluster-zstream-4-20-x9qmdr, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-20-x9qmdr in resource group rg-zstream-upgrade-4-20-w7phnh, error: failed waiting for cluster="cluster-zstream-4-20-x9qmdr" in resourcegroup="rg-zstream-upgrade-4-20-w7phnh" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-20-x9qmdr in resource group rg-zstream-upgrade-4-20-w7phnh, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:141]: Unexpected error:
<*fmt.wrapErrors | 0xc0014b4ff0>:
failed to create HCP cluster cluster-zstream-4-20-x9qmdr, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-20-x9qmdr in resource group rg-zstream-upgrade-4-20-w7phnh, error: failed waiting for cluster="cluster-zstream-4-20-x9qmdr" in resourcegroup="rg-zstream-upgrade-4-20-w7phnh" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-20-x9qmdr in resource group rg-zstream-upgrade-4-20-w7phnh, error: context deadline exceeded
...
occurredContributing tests (2)
Affected runs (2)
| |||||||||||||||||||||||||||||||||||||||||||||||
context deadline exceededfull failure pattern: context deadline exceeded Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s) | e2e | 1 | 16.67%1 of 6 job runs affected | IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 2 day(s) | Show trend detailsMay 7: 2 · May 8: 0 · May 9: 0 · May 10: 0 · May 11: 0 · May 12: 0 · May 13: 1 | none | |||||||||||||||||||||||||||||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:139]: Unexpected error:
<context.deadlineExceededError>:
context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:139]: Unexpected error:
<context.deadlineExceededError>:
context deadline exceeded
...
occurredContributing tests (1)
Affected runs (1)
| |||||||||||||||||||||||||||||||||||||||||||||||
couldn't get current server API group list: the server has asked for the client to provide credentialsfull failure pattern: couldn't get current server API group list: the server has asked for the client to provide credentials Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 2 day(s) | e2e | 1 | 16.67%1 of 6 job runs affected | IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 2 day(s) | Show trend detailsMay 7: 0 · May 8: 1 · May 9: 0 · May 10: 0 · May 11: 0 · May 12: 0 · May 13: 1 | none | |||||||||||||||||||||||||||||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:362]: Timed out after 300.000s.
The function passed to Eventually failed at /opt/app-root/src/github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:347 with:
kubectl should execute successfully from authorized VM with OIDC token
Unexpected error:
<*errors.errorString | 0xc000bef620>:
E0514 00:08:31.255742 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0514 00:08:31.268033 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0514 00:08:31.294823 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0514 00:08:31.307820 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0514 00:08:31.324327 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
error: You must be logged in to the server (the server has asked for the client to provide credentials)
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:362]: Timed out after 300.000s.
The function passed to Eventually failed at /opt/app-root/src/github.com/Azure/ARO-HCP/test/e2e/cluster_authorized_cidrs_connectivity.go:347 with:
kubectl should execute successfully from authorized VM with OIDC token
Unexpected error:
<*errors.errorString | 0xc000bef620>:
E0514 00:08:31.255742 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0514 00:08:31.268033 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0514 00:08:31.294823 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0514 00:08:31.307820 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0514 00:08:31.324327 2644 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
error: You must be logged in to the server (the server has asked for the client to provide credentials)
...
occurredContributing tests (1)
Affected runs (1)
| |||||||||||||||||||||||||||||||||||||||||||||||
DeleteResourceGroup timed out after <minutes> minutes; context deadline exceededfull failure pattern: DeleteResourceGroup timed out after <minutes> minutes; context deadline exceeded Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | e2e | 1 | 16.67%1 of 6 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | Show trend detailsMay 7: 0 · May 8: 0 · May 9: 0 · May 10: 0 · May 11: 0 · May 12: 0 · May 13: 1 | none | |||||||||||||||||||||||||||||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:143]: Unexpected error:
<*fmt.wrapErrors | 0xc00115e660>:
failed to delete resource group, caused by: timeout '60.000000' minutes exceeded during DeleteResourceGroup for resource group cx-rg-cluster-fbqwxv, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_delete_cx_rg.go:143]: Unexpected error:
<*fmt.wrapErrors | 0xc00115e660>:
failed to delete resource group, caused by: timeout '60.000000' minutes exceeded during DeleteResourceGroup for resource group cx-rg-cluster-fbqwxv, error: context deadline exceeded
...
occurredContributing tests (1)
Affected runs (1)
| |||||||||||||||||||||||||||||||||||||||||||||||