Bug 1800628 - [Desheduler] Thresholds are not honored correctly in cluster pod logs
Summary: [Desheduler] Thresholds are not honored correctly in cluster pod logs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.0
Assignee: Mike Dame
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-07 15:09 UTC by RamaKasturi
Modified: 2020-05-04 11:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 11:34:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-descheduler-operator pull 72 0 None closed Bug 1800628: Switch to ghodss yaml package 2020-08-18 05:23:58 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:35:11 UTC

Description RamaKasturi 2020-02-07 15:09:51 UTC
Description of problem:
I see that even after passing right threshold parameters in the kubescheduler/cluster cluster logs reports saying "no  resource threshold is configured" also i see some more params being passed into the configmap even though customer/user do not pass them.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install the kube descheduler operator
2. Now set the lownodeutilization with the params
3. 

Actual results:
I see that the thresholds are passed correctly to configmap/cluster but cluster logs still shows that "I0207 15:06:41.373147       1 lownodeutilization.go:101] no resource threshold is configured" 

  LowNodeUtilization:
        enabled: true
        weight: 0
        params:
          noderesourceutilizationthresholds:
            thresholds:
              cpu: 10
              memory: 20
              pods: 30
            targetthresholds:
              cpu: 10
              memory: 20
              pods: 30
            numberofnodes: 3
          nodeaffinitytype: []
      RemoveDuplicates:
        enabled: true
        weight: 0
        params:
          noderesourceutilizationthresholds:
            thresholds: {}
            targetthresholds: {}
            numberofnodes: 0
          nodeaffinitytype: []
      RemovePodsViolatingInterPodAntiAffinity:
        enabled: true
        weight: 0
        params:
          noderesourceutilizationthresholds:
            thresholds: {}
            targetthresholds: {}
            numberofnodes: 0
          nodeaffinitytype: []
      RemovePodsViolatingNodeAffinity:
        enabled: true
        weight: 0
        params:
          noderesourceutilizationthresholds:
            thresholds: {}
            targetthresholds: {}
            numberofnodes: 0
          nodeaffinitytype:
          - requiredDuringSchedulingIgnoredDuringExecution
      RemovePodsViolatingNodeTaints:
        enabled: true
        weight: 0
        params:
          noderesourceutilizationthresholds:
            thresholds: {}
            targetthresholds: {}
            numberofnodes: 0
          nodeaffinitytype: []


Expected results:
When the thresholds are set descheduler should honor that and the logs should it correctly also configmap should only have params which are passed from the kubescheduler/cluster.

Additional info:

Comment 4 errata-xmlrpc 2020-05-04 11:34:48 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, 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/RHBA-2020:0581


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