When the operator configuration is deployed in different namespace than `openshift-kube-descheduler-operator`, the operator is reporting: ``` E0825 23:53:11.641464 1 target_config_reconciler.go:307] key failed with : kubedeschedulers.operator.openshift.io "cluster" not found ``` The log does not say anything about the namespace. Explicitly mentioning the expected namespace may give user more hints on what's wrong.
Moving the bug to verified state as i see that when descheduler is installed in a namespace other than "openshift-kube-descheduler-operator" following error is seen in the operator logs. [ramakasturinarra@dhcp35-60 ~]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE clusterkubedescheduleroperator.4.6.0-202009192030.p0 Kube Descheduler Operator 4.6.0-202009192030.p0 Succeeded E0921 07:06:38.782182 1 target_config_reconciler.go:94] "unable to get operator configuration" err="kubedeschedulers.operator.openshift.io \"cluster\" not found" namespace="openshift-kube-descheduler-operator" kubedescheduler="cluster" E0921 07:06:38.782206 1 target_config_reconciler.go:467] key failed with : kubedeschedulers.operator.openshift.io "cluster" not found E0921 07:06:38.794083 1 target_config_reconciler.go:94] "unable to get operator configuration" err="kubedeschedulers.operator.openshift.io \"cluster\" not found" namespace="openshift-kube-descheduler-operator" kubedescheduler="cluster" Based on the above moving bug to verified state.
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 (OpenShift Container Platform 4.6 GA Images), 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:4196