-
Bug
-
Resolution: Done
-
Critical
-
4.12
-
None
-
Critical
-
None
-
Approved
-
False
-
-
N/A
-
Release Note Not Required
This is a clone of issue OCPBUGS-3990. The following is the description of the original issue:
—
Description of problem:
This PR fails HyperShift CI fails with:
=== RUN TestAutoscaling/EnsureNoPodsWithTooHighPriority util.go:411: pod csi-snapshot-controller-7bb4b877b4-q5457 with priorityClassName system-cluster-critical has a priority of 2000000000 with exceeds the max allowed of 100002000 util.go:411: pod csi-snapshot-webhook-644b6dbfb-v4lj7 with priorityClassName system-cluster-critical has a priority of 2000000000 with exceeds the max allowed of 100002000
How reproducible:
always
Steps to Reproduce:
- Install HyperShift + create a guest cluster with CSI Snapshot Controller and/or Cluster Storage Operator / AWS EBS CSI driver operator running in the HyperShift managed cluster
- Check priorityClass of the guest control plane pods in the hosted cluster.
Alternatively, ci/prow/e2e-aws in https://github.com/openshift/hypershift/pull/1698 and https://github.com/openshift/hypershift/pull/1748 must pass.
- clones
-
OCPBUGS-3990 HyperShift control plane operators have wrong priorityClass
- Closed
- is blocked by
-
OCPBUGS-3990 HyperShift control plane operators have wrong priorityClass
- Closed
- links to