Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-7876

[Descheduler] Enabling LifeCycleUtilization to test namespace filtering does not work

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.13
    • descheduler
    • None
    • Critical
    • Yes
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when the `LifeCycleUtilization` profile was excluded to test namespace filtering, the following error was logged in the Descheduler Operator logs: `belowE0222 12:43:14.331258 1 target_config_reconciler.go:668] key failed with : only namespace exclusion supported with LowNodeUtilization`. Consequently, the descheduler cluster pod would not start. This issue has been resolved and namespace exclusion now works with the `LifeCycleUtilization` profile. (link:https://issues.redhat.com/browse/OCPBUGS-7876[*OCPBUGS-7876*])
      Show
      * Previously, when the `LifeCycleUtilization` profile was excluded to test namespace filtering, the following error was logged in the Descheduler Operator logs: `belowE0222 12:43:14.331258 1 target_config_reconciler.go:668] key failed with : only namespace exclusion supported with LowNodeUtilization`. Consequently, the descheduler cluster pod would not start. This issue has been resolved and namespace exclusion now works with the `LifeCycleUtilization` profile. (link: https://issues.redhat.com/browse/OCPBUGS-7876 [* OCPBUGS-7876 *])
    • Bug Fix
    • Done

      Description of problem:

      When LifeCycleUtilization is enabled to test namespace filtering i see that an error is logged in the descheduler operator logs and the descheduler cluster pod does not come up

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

      [knarra@knarra ~]$ oc get csv -n openshift-kube-descheduler-operatorNAME                                                 DISPLAY                     VERSION               REPLACES                                             PHASEclusterkubedescheduleroperator.4.13.0-202302091829   Kube Descheduler Operator   4.13.0-202302091829   clusterkubedescheduleroperator.4.13.0-202302090042   Failed

      How reproducible:

      Always

      Steps to Reproduce:

      1. Install 4.13 cluster
2. Install latest descheduler operator
3. Now try creating a descheduler cluster CR with the below profiles enabled
"AffinityAndTaints",
"TopologyAndDuplicates",
"LifecycleAndUtilization"

      Actual results:

      I see that descheduler cluster pod does not come up and descheduler operator logs has the error belowE0222 12:43:14.331258       1 target_config_reconciler.go:668] key failed with : only namespace exclusion supported with LowNodeUtilization

      Expected results:

      Even though namespace inclusion is not supported with LowNodeUtilization an error should not be thrown and a descheduler cluster pod not coming up is not acceptable, since there are other strategies which support namespace filtering.

      Additional info:

      https://redhat-internal.slack.com/archives/GK58XC2G2/p1677069920132399

              rh-ee-lseveroa Lucas Severo Alves (Inactive)
              knarra@redhat.com Rama Kasturi Narra
              Rama Kasturi Narra Rama Kasturi Narra
              Darragh Fitzmaurice Darragh Fitzmaurice
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: