<
Single Day: Apr 15
> Reset
View JSON API

Environment: PROD

Failure patterns: 4 · Failures matched: 6 · Total runs: 7 · Runs affected: 4

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 is valid for <hcp-api-host>, <hcp-api-host>, not <hcp-api-host>
full failure pattern:
tls: failed to verify certificate: x509: certificate is valid for <hcp-api-host>, <hcp-api-host>, not <hcp-api-host>
Signal: FlakeSignal: Flake — present in 2 prior week(s); spread across 3 days
e2e114.29%1 of 7 job runs affectedFlakeSignal: Flake — present in 2 prior week(s); spread across 3 daysShow trend detailsApr 9: 2 · Apr 10: 0 · Apr 11: 0 · Apr 12: 1 · Apr 13: 0 · Apr 14: 0 · Apr 15: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:161]: Unexpected error:
    <*url.Error | 0xc00161c840>: 
    Get "https://api.a5t3f6u4j8a4a5h.o0jt.eastus2.aroapp-hcp.io:443/apis/config.openshift.io/v1/clusterversions/version": tls: failed to verify certificate: x509: certificate is valid for api.a5t3f6u4j8a4a5h.4ufg.eastus2.aroapp-hcp.io, reserved.aroapp-hcp.io, not api.a5t3f6u4j8a4a5h.o0jt.eastus2.aroapp-hcp.io
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:161]: Unexpected error:
    <*url.Error | 0xc00161c840>: 
    Get "https://api.a5t3f6u4j8a4a5h.o0jt.eastus2.aroapp-hcp.io:443/apis/config.openshift.io/v1/clusterversions/version": tls: failed to verify certificate: x509: certificate is valid for api.a5t3f6u4j8a4a5h.4ufg.eastus2.aroapp-hcp.io, reserved.aroapp-hcp.io, not api.a5t3f6u4j8a4a5h.o0jt.eastus2.aroapp-hcp.io
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should upgrade and update a nodepool from 4.20.z to 4.20.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2044346239444586496
expected 4 nodes, found 5
full failure pattern:
expected 4 nodes, found 5
Signal: IndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior history
e2e228.57%2 of 7 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 2 day(s) — New failure pattern — no prior historyShow trend detailsApr 9: 0 · Apr 10: 0 · Apr 11: 0 · Apr 12: 0 · Apr 13: 0 · Apr 14: 2 · Apr 15: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc000ddc1c0>: 
    expected 4 nodes, found 5
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc000ddc1c0>: 
    expected 4 nodes, found 5
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc000ff0ef0>: 
    expected 4 nodes, found 5
    ...
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_update_nodes.go:262]: Expected success, but got an error:
    <*errors.errorString | 0xc000ff0ef0>: 
    expected 4 nodes, found 5
    ...
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to update nodepool replicas and autoscaling2
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2044421226465595392
n/a2044346239444586496
failed waiting for nodepool="<nodepool>" for cluster "<cluster>" in resourcegroup="<resource-group>" to finish creating: context deadline exceeded
full failure pattern:
failed waiting for nodepool="<nodepool>" for cluster "<cluster>" in resourcegroup="<resource-group>" to finish creating: context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)
e2e228.57%2 of 7 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 1 day(s)Show trend detailsApr 9: 0 · Apr 10: 0 · Apr 11: 0 · Apr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 2none
Full failure examples (2)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc00132a1a0>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-7jmwwn" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc00132a1a0>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-7jmwwn" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc000118040>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-hcd2ng" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_cilium.go:186]: Unexpected error:
    <*fmt.wrapError | 0xc000118040>: 
    failed waiting for nodepool="cilium-np" for cluster "cilium-cluster" in resourcegroup="e2e-cilium-hcd2ng" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully2
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2044419001106305024
n/a2044346239444586496
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
CreateNodePoolFromParam timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 1 day(s)
e2e114.29%1 of 7 job runs affectedIndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 1 day(s)Show trend detailsApr 9: 0 · Apr 10: 0 · Apr 11: 0 · Apr 12: 0 · Apr 13: 0 · Apr 14: 0 · Apr 15: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc000cb0660>: 
    failed to create NodePool np-1, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-dwmdj6, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-dwmdj6" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:151]: Unexpected error:
    <*fmt.wrapErrors | 0xc000cb0660>: 
    failed to create NodePool np-1, caused by: timeout '45.000000' minutes exceeded during CreateNodePoolFromParam for node pool np-1 in resource group private-keyvault-dwmdj6, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-dwmdj6" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2044295773960540160