Description of problem: The following test fails: [sig-arch] Managed cluster should ensure control plane pods do not run in best-effort QoS [It] ensure control plane pods do not run in best-effort QoS [Suite:openshift/conformance/parallel] github.com/openshift/origin/test/extended/operators/qos.go:20 Oct 28 08:08:09.079: FAIL: 7 pods found in best-effort QoS: openshift-kuryr/kuryr-cni-cbxgz is running in best-effort QoS openshift-kuryr/kuryr-cni-jk24b is running in best-effort QoS openshift-kuryr/kuryr-cni-px4nl is running in best-effort QoS openshift-kuryr/kuryr-cni-tggzs is running in best-effort QoS openshift-kuryr/kuryr-cni-wqrls is running in best-effort QoS openshift-kuryr/kuryr-cni-zb687 is running in best-effort QoS openshift-kuryr/kuryr-controller-7554b7d58d-jxfkk is running in best-effort QoS Version-Release number of selected component (if applicable): OCP 4.9.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verified with 4.10.0-0.nightly-2022-01-11-065245 Ensured Kuryr pods don't use the BestEffort QoS $ oc get pods -n openshift-kuryr -o name | (xargs -I% oc describe % -n openshift-kuryr|grep QoS) QoS Class: Burstable QoS Class: Burstable QoS Class: Burstable QoS Class: Burstable QoS Class: Burstable QoS Class: Burstable QoS Class: Burstable
Removing the Triaged keyword because: * the QE automation assessment (flag qe_test_coverage) is missing
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056