CIHealth
<
Weekly: May 18 - May 24▾
Last 7 Days Weekly: May 18 - May 24 Sprint: May 11 - May 24 Single Day: May 24
Custom time window
> Reset
View JSON API

Environment: STG

Failure patterns: 7 · Failures matched: 21 · Total runs: 12 · Runs affected: 7

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.
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 — seen in 1 prior week(s); active 3 day(s)
e2e325.00%3 of 12 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 3 day(s)Show trend detailsMay 17: 0 · May 18: 3 · May 19: 2 · May 20: 0 · May 21: 2 · May 22: 0 · May 23: 0 · May 24: 0none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:262] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc000d525e8>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="hcp-cluster-np-128" in resourcegroup="clusternp128-bjt9bn" 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:262] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc000d525e8>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="hcp-cluster-np-128" in resourcegroup="clusternp128-bjt9bn" 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:262] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc0010f8138>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="cluster-candidate-4-20-xhwfzs" in resourcegroup="rg-candidate-4-20-xchgmf" 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:262] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc0010f8138>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="cluster-candidate-4-20-xhwfzs" in resourcegroup="rg-candidate-4-20-xchgmf" 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:262] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc000bb4540>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="cluster-np-labels-taints" in resourcegroup="rg-np-labels-taints-jjhg79" 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:262] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc000bb4540>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="cluster-np-labels-taints" in resourcegroup="rg-np-labels-taints-jjhg79" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
Contributing tests (7)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create a HCP cluster and use cilium CNI plugin1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create a cluster with an external auth config and get the external auth config1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to update node pool labels and taints1
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should upgrade and update a nodepool from 4.21.z to 4.21.zLatest1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.201
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster and custom node pool osDisk size1
Affected runs (3)
Date (UTC)Associated PRProw job
n/a2057280444499496960
n/a2056763447567192064
n/a2056331766691532800
timeout during CreateHCPClusterAndWait; context deadline exceeded
full failure pattern:
timeout during CreateHCPClusterAndWait; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 2 day(s)
e2e216.67%2 of 12 job runs affectedIndeterminateSignal: Indeterminate — seen in 4 prior week(s); active 2 day(s)Show trend detailsMay 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 8 · May 23: 1 · May 24: 0none
Full failure examples (3)
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:158]: failed to create HCP cluster "cp-ystream-upgrade-4-22-24644n" with install version 4.21.16
Unexpected error:
    <*fmt.wrapErrors | 0xc000aa96e0>: 
    failed to create HCP cluster cp-ystream-upgrade-4-22-24644n, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-22-24644n in resource group rg-cp-ystream-upgrade-4-22-xpdwqm, error: failed waiting for cluster="cp-ystream-upgrade-4-22-24644n" in resourcegroup="rg-cp-ystream-upgrade-4-22-xpdwqm" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-22-24644n in resource group rg-cp-ystream-upgrade-4-22-xpdwqm, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_minor_upgrade.go:158]: failed to create HCP cluster "cp-ystream-upgrade-4-22-24644n" with install version 4.21.16
Unexpected error:
    <*fmt.wrapErrors | 0xc000aa96e0>: 
    failed to create HCP cluster cp-ystream-upgrade-4-22-24644n, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-22-24644n in resource group rg-cp-ystream-upgrade-4-22-xpdwqm, error: failed waiting for cluster="cp-ystream-upgrade-4-22-24644n" in resourcegroup="rg-cp-ystream-upgrade-4-22-xpdwqm" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cp-ystream-upgrade-4-22-24644n in resource group rg-cp-ystream-upgrade-4-22-xpdwqm, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:120]: Swift cluster rg-candidate-5-0-7jt2zr/cluster-candidate-5-0-898h7z should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000a159e0>: 
    failed waiting for cluster="cluster-candidate-5-0-898h7z" in resourcegroup="rg-candidate-5-0-7jt2zr" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-candidate-5-0-898h7z in resource group rg-candidate-5-0-7jt2zr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:120]: Swift cluster rg-candidate-5-0-7jt2zr/cluster-candidate-5-0-898h7z should provision
Unexpected error:
    <*fmt.wrapErrors | 0xc000a159e0>: 
    failed waiting for cluster="cluster-candidate-5-0-898h7z" in resourcegroup="rg-candidate-5-0-7jt2zr" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPCluster20251223AndWait for cluster cluster-candidate-5-0-898h7z in resource group rg-candidate-5-0-7jt2zr, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:137]: failed to create HCP cluster "cluster-zstream-4-22-9dtk7p" with version 4.22.0-rc.2 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc00114e9f0>: 
    failed to create HCP cluster cluster-zstream-4-22-9dtk7p, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-9dtk7p in resource group rg-zstream-upgrade-4-22-68pdm8, error: failed waiting for cluster="cluster-zstream-4-22-9dtk7p" in resourcegroup="rg-zstream-upgrade-4-22-68pdm8" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-9dtk7p in resource group rg-zstream-upgrade-4-22-68pdm8, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/control_plane_automated_z_stream_upgrade.go:137]: failed to create HCP cluster "cluster-zstream-4-22-9dtk7p" with version 4.22.0-rc.2 on candidate channel
Unexpected error:
    <*fmt.wrapErrors | 0xc00114e9f0>: 
    failed to create HCP cluster cluster-zstream-4-22-9dtk7p, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-9dtk7p in resource group rg-zstream-upgrade-4-22-68pdm8, error: failed waiting for cluster="cluster-zstream-4-22-9dtk7p" in resourcegroup="rg-zstream-upgrade-4-22-68pdm8" to finish creating, caused by: timeout '20.000000' minutes exceeded during CreateHCPClusterFromParam for cluster cluster-zstream-4-22-9dtk7p in resource group rg-zstream-upgrade-4-22-68pdm8, error: context deadline exceeded
    ...
occurred
Contributing tests (9)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.201
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 5.01
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelAuthorized CIDRs Connectivity should allow API access only from authorized VM IP1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCreate HCPOpenShiftCluster with Private KeyVault should create a cluster with private keyvault using v20251223preview API1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to successfully upgrade control plane minor version from 4.21 minor to 4.22 minor1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should create an HCP cluster and validate TLS certificates1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should not be able to reuse subnets and NSGs between clusters1
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelService Provider should upgrade the control plane z-stream automatically on behalf of the customer for 4.221
Affected runs (2)
Date (UTC)Associated PRProw job
n/a2058004991464968192
n/a2057642836106416128
context deadline exceeded
full failure pattern:
context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)
e2e18.33%1 of 12 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsMay 17: 0 · May 18: 0 · May 19: 0 · May 20: 1 · May 21: 0 · May 22: 0 · May 23: 0 · May 24: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057028999443386368
ERROR CODE: InvalidRequestContent; detail message Duplicate ARO-HCP cluster <cluster>. An ARO-HCP cluster <cluster> name 'cluster-candidate-4-21-lwfbjc', Azure Subscription ID 'XX...
full failure pattern:
ERROR CODE: InvalidRequestContent; detail message Duplicate ARO-HCP cluster <cluster>. An ARO-HCP cluster <cluster> name 'cluster-candidate-4-21-lwfbjc', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure resource group <resource-group> 'rg-candidate-4-21-cgh878' already exists; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e18.33%1 of 12 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 17: 0 · May 18: 0 · May 19: 0 · May 20: 1 · May 21: 0 · May 22: 0 · May 23: 0 · May 24: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:109]: Unexpected error:
    <*fmt.wrapError | 0xc00133ac60>: 
    failed to create HCP cluster cluster-candidate-4-21-lwfbjc: failed starting cluster creation "cluster-candidate-4-21-lwfbjc" in resourcegroup="rg-candidate-4-21-cgh878": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-candidate-4-21-cgh878/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-candidate-4-21-lwfbjc
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Duplicate ARO-HCP cluster name. An ARO-HCP cluster with name 'cluster-candidate-4-21-lwfbjc', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure Resource group name 'rg-candidate-4-21-cgh878' already exists"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:109]: Unexpected error:
    <*fmt.wrapError | 0xc00133ac60>: 
    failed to create HCP cluster cluster-candidate-4-21-lwfbjc: failed starting cluster creation "cluster-candidate-4-21-lwfbjc" in resourcegroup="rg-candidate-4-21-cgh878": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-candidate-4-21-cgh878/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-candidate-4-21-lwfbjc
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Duplicate ARO-HCP cluster name. An ARO-HCP cluster with name 'cluster-candidate-4-21-lwfbjc', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure Resource group name 'rg-candidate-4-21-cgh878' already exists"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.211
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2056917934470598656
RevokeCredentialsAndWait timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
RevokeCredentialsAndWait timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e18.33%1 of 12 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 17: 0 · May 18: 0 · May 19: 0 · May 20: 1 · May 21: 0 · May 22: 0 · May 23: 0 · May 24: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:252]: Unexpected error:
    <*fmt.wrapErrors | 0xc000bcc3c0>: 
    failed waiting for hcpCluster="admin-cred-lifecycle-n6spml" in resourcegroup="admin-credential-lifecycle-test-lk87zw" to finish revoking creds, caused by: timeout '15.000000' minutes exceeded during RevokeCredentialsAndWait for cluster admin-cred-lifecycle-n6spml in resource group admin-credential-lifecycle-test-lk87zw, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:252]: Unexpected error:
    <*fmt.wrapErrors | 0xc000bcc3c0>: 
    failed waiting for hcpCluster="admin-cred-lifecycle-n6spml" in resourcegroup="admin-credential-lifecycle-test-lk87zw" to finish revoking creds, caused by: timeout '15.000000' minutes exceeded during RevokeCredentialsAndWait for cluster admin-cred-lifecycle-n6spml in resource group admin-credential-lifecycle-test-lk87zw, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057028999443386368
failed to wait for first cluster "<cluster>" to complete creation
full failure pattern:
failed to wait for first cluster "<cluster>" to complete creation
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e18.33%1 of 12 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 1 · May 23: 0 · May 24: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: failed to wait for first cluster "basic-hcp-cluster" to complete creation
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: failed to wait for first cluster "basic-hcp-cluster" to complete creation
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057642836106416128
validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-n12p2cds:stage-e2e-parallel" cannot get ...
full failure pattern:
validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-n12p2cds:stage-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
e2e18.33%1 of 12 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 17: 0 · May 18: 0 · May 19: 0 · May 20: 0 · May 21: 0 · May 22: 1 · May 23: 0 · May 24: 0none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:135]: ValidatingAdmissionPolicy should exist
Unexpected error:
    <*errors.StatusError | 0xc000e0e140>: 
    validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-n12p2cds:stage-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 | 0xc000e0e140>: 
    validatingadmissionpolicies.admissionregistration.k8s.io "image-registry-allowlist-policy" is forbidden: User "system:serviceaccount:ci-op-n12p2cds:stage-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-stage-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/a2057642836106416128