Bug 1990603 - [Descheduler] descheduler operator throws an error which reads "key failed with : scheduler.config.openshift.io "cluster" not found"
Summary: [Descheduler] descheduler operator throws an error which reads "key failed wi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.0
Assignee: Mike Dame
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-05 17:26 UTC by RamaKasturi
Modified: 2021-10-18 17:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:45:05 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 207 0 None None None 2021-08-09 19:32:59 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:45:20 UTC

Description RamaKasturi 2021-08-05 17:26:38 UTC
Description of problem:
I see that descheduler cluster object is not present in the descheduler operator manespace when installed latest descheduler operator & also descheduler operator log complains about it cannot find "scheduler.config.openshift.io "cluster" not found" which is incorrect

Version-Release number of selected component (if applicable):
[knarra@knarra openshift-tests-private]$ oc get csv
NAME                                                DISPLAY                     VERSION              REPLACES   PHASE
clusterkubedescheduleroperator.4.9.0-202108050954   Kube Descheduler Operator   4.9.0-202108050954              Succeeded


How reproducible:
Always

Steps to Reproduce:
1. Install latest descheduler operator
2. Creae kubedescheduler cluster object
3.

Actual results:
kubedescheduler cluster object appears in the UI but when running "oc get pods -n openshift-kube-descheduler-operator" only see below in the namespace
[knarra@knarra openshift-tests-private]$ oc get pods -n openshift-kube-descheduler-operator
NAME                                    READY   STATUS    RESTARTS   AGE
descheduler-operator-5956bb79b9-ck69n   1/1     Running   0          15m

Also descheduler operator log complains the below that it cannot find scheduler cluster which is incorrect as well

I0805 17:10:38.274219       1 shared_informer.go:247] Caches are synced for RequestHeaderAuthRequestController 
I0805 17:10:38.274253       1 shared_informer.go:247] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file 
I0805 17:10:38.274332       1 shared_informer.go:247] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file 
I0805 17:10:38.287554       1 base_controller.go:73] Caches are synced for LoggingSyncer 
I0805 17:10:38.287579       1 base_controller.go:110] Starting #1 worker of LoggingSyncer controller ...
E0805 17:11:57.819055       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:11:57.828356       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:11:57.842275       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:11:57.866467       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:11:57.910460       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:11:57.995242       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:11:58.159966       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:11:58.485792       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:11:59.131631       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:12:00.417955       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:12:02.985573       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:12:08.112854       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:12:18.361985       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:12:38.850987       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:13:19.818540       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found
E0805 17:14:41.748883       1 target_config_reconciler.go:412] key failed with : scheduler.config.openshift.io "cluster" not found


Expected results:
Descheduler cluster should be available and should work fine.

Additional info:

Comment 2 RamaKasturi 2021-08-14 10:57:52 UTC
Verified with the build below and i see that creating kubedescheduler cluster object works fine with out any issues.

[knarra@knarra openshift-client-linux-4.9.0-0.nightly-2021-08-14-044521]$ oc get csv -n openshift-kube-descheduler-operator
NAME                                                DISPLAY                     VERSION              REPLACES   PHASE
clusterkubedescheduleroperator.4.9.0-202108130204   Kube Descheduler Operator   4.9.0-202108130204              Succeeded

Based on the above moving bug to verified state.

Comment 5 errata-xmlrpc 2021-10-18 17:45:05 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.9.0 bug fix and 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-2021:3759


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