Bug 2039414 - Cannot see the weights increased for NodeAffinity, InterPodAffinity, TaintandToleration
Summary: Cannot see the weights increased for NodeAffinity, InterPodAffinity, Taintand...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: ravig
QA Contact: RamaKasturi
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-11 17:05 UTC by RamaKasturi
Modified: 2023-09-15 01:18 UTC (History)
3 users (show)

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])
Clone Of:
Last Closed: 2022-03-12 04:40:54 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-scheduler-operator pull 395 0 None open Bug 2039414: Update KubeSchedulerConfig to v1beta3(default in 1.23) 2022-01-17 14:09:52 UTC
Github openshift kubernetes pull 1121 0 None open Bug 2039414: Stop using component config 2022-01-17 14:10:09 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:41:06 UTC

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
version   4.10.0-fc.0   True        False         6h25m   Cluster version is 4.10.0-fc.0

How reproducible:

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

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

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.


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

Note You need to log in before you can comment on or make changes to this bug.