Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2018093

Summary: Managed cluster should ensure control plane pods do not run in best-effort QoS
Product: OpenShift Container Platform Reporter: Itzik Brown <itbrown>
Component: NetworkingAssignee: Michał Dulko <mdulko>
Networking sub component: kuryr QA Contact: Itzik Brown <itbrown>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium    
Version: 4.9   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:22:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Itzik Brown 2021-10-28 08:28:04 UTC 
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:
Comment 3 Itzik Brown 2022-01-13 07:10:32 UTC 
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
Comment 5 ShiftStack Bugwatcher 2022-03-05 07:07:19 UTC 
Removing the Triaged keyword because:
* the QE automation assessment (flag qe_test_coverage) is missing
Comment 7 errata-xmlrpc 2022-03-10 16:22:54 UTC 
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