No failure patterns match your search.
Environment: INT
Failure patterns: 2 · Failures matched: 7 · Total runs: 4 · Runs affected: 3
| 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. | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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 | 3 | 75.00%3 of 4 job runs affected | IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s) | Show trend detailsJun 18: 0 · Jun 19: 0 · Jun 20: 0 · Jun 21: 0 · Jun 22: 0 · Jun 23: 0 · Jun 24: 6 | none | ||||||||||||||||||||||||||||||||||||
Full failure examples (3)fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:102]: failed to create HCP cluster "cluster-zstream-4-22-hc9vcx" with version 4.22.0 on candidate channel
Unexpected error:
<*fmt.wrapErrors | 0xc00165f230>:
failed to create HCP cluster cluster-zstream-4-22-hc9vcx, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-hc9vcx in resource group rg-zstream-upgrade-4-22-b2z8v8, error: failed waiting for cluster="cluster-zstream-4-22-hc9vcx" in resourcegroup="rg-zstream-upgrade-4-22-b2z8v8" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-hc9vcx in resource group rg-zstream-upgrade-4-22-b2z8v8, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:102]: failed to create HCP cluster "cluster-zstream-4-22-hc9vcx" with version 4.22.0 on candidate channel
Unexpected error:
<*fmt.wrapErrors | 0xc00165f230>:
failed to create HCP cluster cluster-zstream-4-22-hc9vcx, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-hc9vcx in resource group rg-zstream-upgrade-4-22-b2z8v8, error: failed waiting for cluster="cluster-zstream-4-22-hc9vcx" in resourcegroup="rg-zstream-upgrade-4-22-b2z8v8" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-hc9vcx in resource group rg-zstream-upgrade-4-22-b2z8v8, error: context deadline exceeded
...
occurredfail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:102]: failed to create HCP cluster "cluster-zstream-4-22-f775mx" with version 4.22.0 on candidate channel
Unexpected error:
<*fmt.wrapErrors | 0xc000c6e300>:
failed to create HCP cluster cluster-zstream-4-22-f775mx, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-f775mx in resource group rg-zstream-upgrade-4-22-pztvl9, error: failed waiting for cluster="cluster-zstream-4-22-f775mx" in resourcegroup="rg-zstream-upgrade-4-22-pztvl9" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-f775mx in resource group rg-zstream-upgrade-4-22-pztvl9, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:102]: failed to create HCP cluster "cluster-zstream-4-22-f775mx" with version 4.22.0 on candidate channel
Unexpected error:
<*fmt.wrapErrors | 0xc000c6e300>:
failed to create HCP cluster cluster-zstream-4-22-f775mx, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-f775mx in resource group rg-zstream-upgrade-4-22-pztvl9, error: failed waiting for cluster="cluster-zstream-4-22-f775mx" in resourcegroup="rg-zstream-upgrade-4-22-pztvl9" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-f775mx in resource group rg-zstream-upgrade-4-22-pztvl9, error: context deadline exceeded
...
occurredfail [github.com/Azure/ARO-HCP/test/e2e/cluster_version_backlevel.go:148]: failed to create HCP cluster version 4.19
Unexpected error:
<*fmt.wrapErrors | 0xc001454060>:
failed waiting for cluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-8n6ghx" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterAndWait for cluster cluster-ver-4-19 in resource group rg-cluster-back-version-8n6ghx, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_version_backlevel.go:148]: failed to create HCP cluster version 4.19
Unexpected error:
<*fmt.wrapErrors | 0xc001454060>:
failed waiting for cluster="cluster-ver-4-19" in resourcegroup="rg-cluster-back-version-8n6ghx" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterAndWait for cluster cluster-ver-4-19 in resource group rg-cluster-back-version-8n6ghx, error: context deadline exceeded
...
occurredContributing tests (5)
Affected runs (3)
| ||||||||||||||||||||||||||||||||||||||||||
Cluster should become ready within '20.000000' minutesfull failure pattern: Cluster should become ready within '20.000000' minutes Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s) | e2e | 1 | 25.00%1 of 4 job runs affected | IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s) | Show trend detailsJun 18: 0 · Jun 19: 0 · Jun 20: 0 · Jun 21: 0 · Jun 22: 0 · Jun 23: 0 · Jun 24: 1 | none | ||||||||||||||||||||||||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:162]: Timed out after 1200.001s.
Cluster should become ready within '20.000000' minutes
Expected
<bool>: ...
to be true
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:162]: Timed out after 1200.001s.
Cluster should become ready within '20.000000' minutes
Expected
<bool>: ...
to be trueContributing tests (1)
Affected runs (1)
| ||||||||||||||||||||||||||||||||||||||||||