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

Bug 1947771

Summary:	[kube-descheduler]descheduler operator pod should not run as “BestEffort” qosClass
Product:	OpenShift Container Platform	Reporter:	zhou ying <yinzhou>
Component:	kube-scheduler	Assignee:	Jan Chaloupka <jchaloup>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.8	CC:	aos-bugs, jchaloup, mfojtik
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 22:58:26 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:
Bug Depends On:
Bug Blocks:	1948267

Description zhou ying 2021-04-09 08:34:44 UTC

Description of problem:
descheduler operator pod should not run as “BestEffort” qosClass

Version-Release number of selected component (if applicable):
[root@localhost verification-tests]# oc get csv  clusterkubedescheduleroperator.4.8.0-202104072252.p0  -n openshift-kube-descheduler-operator
NAME                                                   DISPLAY                     VERSION                 REPLACES   PHASE
clusterkubedescheduleroperator.4.8.0-202104072252.p0   Kube Descheduler Operator   4.8.0-202104072252.p0              Succeeded

How reproducible:
Always

Steps to Reproduce:
1) Check the descheduler-operator pod status by command: 
`oc get po descheduler-operator-6c7dc99c6c-n5xhj -o json -n openshift-kube-descheduler-operator |jq .status.qosClass`

Actual results:
1) Show the descheduler operator pod runs as “BestEffort” qosClass
[root@localhost verification-tests]# oc get po descheduler-operator-6c7dc99c6c-n5xhj -o json -n openshift-kube-descheduler-operator |jq .status.qosClass 
"BestEffort"


Expected results:
1) Should set cpu/memory limits/request for the descheduler operator pod.

Additional info:

Comment 1 Jan Chaloupka 2021-04-09 09:52:12 UTC

PR awaiting review

Comment 4 RamaKasturi 2021-04-14 11:45:13 UTC

Verified in the csv below and i now see that descheduler pod run as a "Burstable" pod.

[knarra@knarra openshift-client-linux-4.8.0-0.nightly-2021-04-13-171608]$ ./oc get csv -n openshift-kube-descheduler-operator
NAME                                                   DISPLAY                     VERSION                 REPLACES   PHASE
clusterkubedescheduleroperator.4.8.0-202104121740.p0   Kube Descheduler Operator   4.8.0-202104121740.p0              Succeeded

[knarra@knarra openshift-client-linux-4.8.0-0.nightly-2021-04-13-171608]$ ./oc get pod descheduler-operator-77545bff45-zwg66 -o json -n openshift-kube-descheduler-operator |jq .status.qosClass
"Burstable"

 "resources": {
                    "requests": {
                        "cpu": "10m",
                        "memory": "50Mi"
                    }

[knarra@knarra openshift-client-linux-4.8.0-0.nightly-2021-04-13-171608]$ ./oc get pod openshift-kube-scheduler-operator-865bd594c7-6826n -o json -n openshift-kube-scheduler-operator | grep "cpu"
                        "cpu": "10m",
[knarra@knarra openshift-client-linux-4.8.0-0.nightly-2021-04-13-171608]$ ./oc get pod openshift-kube-scheduler-operator-865bd594c7-6826n -o json -n openshift-kube-scheduler-operator | grep "memory"
                        "memory": "50Mi"
                "key": "node.kubernetes.io/memory-pressure",

Based on the above moving bug to verified state.

Comment 5 RamaKasturi 2021-04-20 11:06:41 UTC

csv & build details where this was verified.

[knarra@knarra openshift-client-linux-4.7.0-0.nightly-2021-04-17-022838]$ ./oc get csv
NAME                                                   DISPLAY                     VERSION                 REPLACES   PHASE
clusterkubedescheduleroperator.4.7.0-202104142050.p0   Kube Descheduler Operator   4.7.0-202104142050.p0              Succeeded
[knarra@knarra openshift-client-linux-4.7.0-0.nightly-2021-04-17-022838]$ ./oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-04-17-022838   True        False         4h52m   Cluster version is 4.7.0-0.nightly-2021-04-17-022838

Comment 8 errata-xmlrpc 2021-07-27 22:58:26 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.8.2 bug fix and 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-2021:2438