<
Single Day: May 22
> Reset
View JSON API

Environment: PROD

Failure patterns: 2 · Failures matched: 2 · Total runs: 3 · Runs affected: 2

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.
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 4 prior week(s); active 1 day(s)
e2e133.33%1 of 3 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 1 day(s)Show trend detailsMay 16: 0 · May 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:153]: Unexpected error:
    <*fmt.wrapErrors | 0xc000f9d8f0>: 
    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-4tjb6l, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-4tjb6l" to finish creating: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_private_kv.go:153]: Unexpected error:
    <*fmt.wrapErrors | 0xc000f9d8f0>: 
    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-4tjb6l, error: failed waiting for nodepool="np-1" for cluster "private-kv-cluster" in resourcegroup="private-keyvault-4tjb6l" to finish creating: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-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/a2057659139126988800
validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-qsh0k34v:prod-e2e-parallel" cannot get r...
full failure pattern:
validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-qsh0k34v:prod-e2e-parallel" cannot get resource "validatingadmissionpolicies" in API group
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e133.33%1 of 3 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 16: 0 · May 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:135]: ValidatingAdmissionPolicy should exist
Unexpected error:
    <*errors.StatusError | 0xc00101e280>: 
    validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-qsh0k34v:prod-e2e-parallel" cannot get resource "validatingadmissionpolicies" in API group "admissionregistration.k8s.io" at the cluster scope
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:135]: ValidatingAdmissionPolicy should exist
Unexpected error:
    <*errors.StatusError | 0xc00101e280>: 
    validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-qsh0k34v:prod-e2e-parallel" cannot get resource "validatingadmissionpolicies" in API group "admissionregistration.k8s.io" at the cluster scope
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelImage Registry Policy should allow pods with images from allowed registries and have a valid allowlist1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057642836072861696