Bug 1920619

Summary: Remove default scheduler profile value
Product: OpenShift Container Platform Reporter: Andrea Hoffer <ahoffer>
Component: kube-schedulerAssignee: Mike Dame <mdame>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: aos-bugs, maszulik, mdame, mfojtik
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:56:23 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 Andrea Hoffer 2021-01-26 18:17:54 UTC
Description of problem: Scheduling profiles are tech preview for 4.7, so users should have to opt in to use them. Right now, there is a default value of LowNodeUtilization for spec.profiles in the scheduler object. There should not be a value (or the field shown at all) by default.

Comment 2 Maciej Szulik 2021-01-27 10:46:04 UTC
We need the bump the API still in a few places.

Comment 4 Maciej Szulik 2021-02-02 10:00:34 UTC
Still need to bump cluster-config-operator

Comment 6 RamaKasturi 2021-02-05 13:35:51 UTC
Verified bug with the payload below and i see that default value of LowNodeUtilization for spec.profile is not present  in the scheduler object.

[knarra@knarra ~]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-02-05-053408   True        False         164m    Cluster version is 4.7.0-0.nightly-2021-02-05-053408

After the fix:
====================
[knarra@knarra ~]$ oc get scheduler cluster -o yaml -n openshift-kube-scheduler
apiVersion: config.openshift.io/v1
kind: Scheduler
metadata:
  creationTimestamp: "2021-02-05T10:18:35Z"
  generation: 1
  managedFields:
  - apiVersion: config.openshift.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        .: {}
        f:mastersSchedulable: {}
        f:policy:
          .: {}
          f:name: {}
      f:status: {}
    manager: cluster-bootstrap
    operation: Update
    time: "2021-02-05T10:18:35Z"
  name: cluster
  resourceVersion: "596"
  selfLink: /apis/config.openshift.io/v1/schedulers/cluster
  uid: 5b7fc7f4-85c7-4d9f-9522-32ed57187916
spec:
  mastersSchedulable: false
  policy:
    name: ""
status: {}

Before the fix:
====================
[knarra@knarra ~]$ oc get scheduler cluster -n openshift-kube-scheduler -o yaml
apiVersion: config.openshift.io/v1
kind: Scheduler
metadata:
  creationTimestamp: "2021-02-04T17:25:22Z"
  generation: 1
  managedFields:
  - apiVersion: config.openshift.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        .: {}
        f:mastersSchedulable: {}
        f:policy:
          .: {}
          f:name: {}
        f:profile: {}
      f:status: {}
    manager: cluster-bootstrap
    operation: Update
    time: "2021-02-04T17:25:22Z"
  name: cluster
  resourceVersion: "552"
  selfLink: /apis/config.openshift.io/v1/schedulers/cluster
  uid: 30ac091f-332d-4010-8e69-a36e10bda258
spec:
  mastersSchedulable: false
  policy:
    name: ""
  profile: LowNodeUtilization
status: {}

Based on the above moving bug to verified state.

Comment 9 errata-xmlrpc 2021-02-24 15:56:23 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.7.0 security, bug fix, and enhancement 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-2020:5633