Bug 2039414

Summary: Cannot see the weights increased for NodeAffinity, InterPodAffinity, TaintandToleration
Product: OpenShift Container Platform Reporter: RamaKasturi <knarra>
Component: kube-schedulerAssignee: ravig <rgudimet>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: high Docs Contact:
Priority: high    
Version: 4.9CC: aos-bugs, mfojtik, rgudimet
Target Milestone: ---Keywords: TestBlocker
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
* Before this update, upgrading to the current release didn't set the correct weights for the `TaintandToleration`, `NodeAffinity`, and `InterPodAffinity` parameters. This update resolves the issue so that upgrading correctly sets the weights for `TaintandToleration` to `3`, `NodeAffinity` to `2`, and `InterPodAffinity` to `2`. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2039414[BZ#2039414])
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-12 04:40: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 RamaKasturi 2022-01-11 17:05:32 UTC
Description of problem:
Tried to perform an upgrade from 4.9 to 4.10(custom build with kuberebase) and i see that the weights of NodeAffinity, InterPodAffinity, TaintAndToleration does not look as below.

TaintToleration 3
NodeAffinity 2
InterPodAffinity 2

Version-Release number of selected component (if applicable):
[knarra@knarra ~]$ oc get clusterversion
NAME      VERSION       AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-fc.0   True        False         6h25m   Cluster version is 4.10.0-fc.0


How reproducible:
Always

Steps to Reproduce:
1. Install 4.9 and upgrade to custom build which has the kuberebase to 1.23
2.
3.

Actual results:
I see that the weights for below did not change as expected.


Expected results:
Weights should be as below

TaintToleration 3
NodeAffinity 2
InterPodAffinity 2


Additional info:
Cause could because of below & it should be v1beta3
https://github.com/openshift/cluster-kube-scheduler-operator/pull/386/commits/ac19dc2b8a3c962f9376b965748690025792b69d

Comment 1 Maciej Szulik 2022-01-12 12:04:53 UTC
This is most likely b/c we still didn't land k8s bump from https://github.com/openshift/kubernetes/pull/1087

Comment 2 RamaKasturi 2022-01-17 17:21:17 UTC
Adding TestBlocker keyword since the bug is preveting QE from testing WRKLDS-279

Comment 6 RamaKasturi 2022-01-24 16:32:13 UTC
Verified with the payload below and i see that weights are as below.

[knarra@knarra ~]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-0.nightly-2022-01-24-020644   True        False         3h12m   Cluster version is 4.10.0-0.nightly-2022-01-24-020644


- name: TaintToleration
        weight: 3

- name: NodeAffinity
        weight: 2

- name: InterPodAffinity
        weight: 2

Below are the procedure i have followed to test the same:
============================================================
1) Install 4.9 cluster
2) change the scheduler operator loglevel to TraceAll
3) Now upgrade the cluster to 4.10
4) Verify for the above weights in the scheduler logs and i can see that they have been updated.

I see that the total time it took for upgrade is above 70minutes. Based on the above moving bug to verified state.

Comment 10 errata-xmlrpc 2022-03-12 04:40: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

Comment 11 Red Hat Bugzilla 2023-09-15 01:18:40 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days