No failure patterns match your search.
Environment: PROD
Failure patterns: 3 · Failures matched: 3 · Total runs: 10 · 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. | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
tls: failed to verify certificate: x509: certificate signed by unknown authorityfull failure pattern: tls: failed to verify certificate: x509: certificate signed by unknown authority Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 3 day(s) | e2e | 1 | 10.00%1 of 10 job runs affected | IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 3 day(s) | Show trend detailsMay 10: 0 · May 11: 0 · May 12: 1 · May 13: 1 · May 14: 0 · May 15: 0 · May 16: 1 | none | ||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:175]: Unexpected error:
<*fmt.wrapError | 0xc00045f2a0>:
route host was never found: Get "https://agnhost-e2e-serving-app-ssw7m.apps.aro.i8p5a8p3n4h1h0k.ioif.brazilsouth.aroapp-hcp.io": tls: failed to verify certificate: x509: certificate signed by unknown authority
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:175]: Unexpected error:
<*fmt.wrapError | 0xc00045f2a0>:
route host was never found: Get "https://agnhost-e2e-serving-app-ssw7m.apps.aro.i8p5a8p3n4h1h0k.ioif.brazilsouth.aroapp-hcp.io": tls: failed to verify certificate: x509: certificate signed by unknown authority
...
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 4 prior week(s); active 1 day(s) | e2e | 1 | 10.00%1 of 10 job runs affected | IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s) | Show trend detailsMay 10: 0 · May 11: 0 · May 12: 0 · May 13: 0 · May 14: 0 · May 15: 0 · May 16: 1 | none | ||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/arm64_nodepool.go:90]: Unexpected error:
<*fmt.wrapErrors | 0xc000bc92c0>:
failed to create HCP cluster arm64-vm-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-vvj79d, error: failed waiting for cluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-vvj79d" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-vvj79d, error: context deadline exceeded
...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/arm64_nodepool.go:90]: Unexpected error:
<*fmt.wrapErrors | 0xc000bc92c0>:
failed to create HCP cluster arm64-vm-hcp-cluster, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-vvj79d, error: failed waiting for cluster="arm64-vm-hcp-cluster" in resourcegroup="arm64-vm-cluster-vvj79d" to finish creating, caused by: timeout '45.000000' minutes exceeded during CreateHCPClusterFromParam for cluster arm64-vm-hcp-cluster in resource group arm64-vm-cluster-vvj79d, error: context deadline exceeded
...
occurredContributing tests (1)
Affected runs (1)
| ||||||||||||||||||||
x509: certificate signed by unknown authorityfull failure pattern: x509: certificate signed by unknown authority Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | e2e | 1 | 10.00%1 of 10 job runs affected | IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history | Show trend detailsMay 10: 0 · May 11: 0 · May 12: 0 · May 13: 0 · May 14: 0 · May 15: 0 · May 16: 1 | none | ||||||||||||||
Full failure examples (1)fail [github.com/Azure/ARO-HCP/test/e2e/cluster_tls_endpoints.go:155]: 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:155]: 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)
| ||||||||||||||||||||