Bug 2058692

Summary: [Secondary Scheduler] Creating secondaryscheduler instance fails with error "key failed with : secondaryschedulers.operator.openshift.io "secondary-scheduler" not found"
Product: OpenShift Container Platform Reporter: RamaKasturi <knarra>
Component: kube-schedulerAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.10CC: aos-bugs, jchaloup, mfojtik
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 10:51:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RamaKasturi 2022-02-25 16:09:44 UTC 
Description of problem:
After creating secondary scheduler instance i do not see the pod being present in the openshift-secondary-scheduler-operator namespace and on further checking it looks like secondary-scheduler-operator is expecting the CR as secondary-scheduler and not cluster. Currently the name of the CR is cluster.

Version-Release number of selected component (if applicable):
secondary-scheduler-operator-container-v1.0-5

How reproducible:
Always

Steps to Reproduce:
1. Install latest available SSO
2. Try creating SSO instance
3.

Actual results:
I can see that secondary scheduler instance does not get created and below logs are seen in the SSO logs.
E0225 13:05:03.939938       1 target_config_reconciler.go:87] "unable to get operator configuration" err="secondaryschedulers.operator.openshift.io \"secondary-scheduler\" not found" namespace="openshift-secondary-scheduler-operator" secondary-scheduler="secondary-scheduler"
E0225 13:05:03.939953       1 target_config_reconciler.go:278] key failed with : secondaryschedulers.operator.openshift.io "secondary-scheduler" not found
E0225 13:09:52.325927       1 base_controller.go:253] LoggingSyncer reconciliation failed: secondaryschedulers.operator.openshift.io "secondary-scheduler" not found
E0225 13:09:52.498251       1 target_config_reconciler.go:87] "unable to get operator configuration" err="secondaryschedulers.operator.openshift.io \"secondary-scheduler\" not found" namespace="openshift-secondary-scheduler-operator" secondary-scheduler="secondary-scheduler"
E0225 13:09:52.498273       1 target_config_reconciler.go:278] key failed with : secondaryschedulers.operator.openshift.io "secondary-scheduler" not found
E0225 13:15:03.939476       1 base_controller.go:253] LoggingSyncer reconciliation failed: secondaryschedulers.operator.openshift.io "secondary-scheduler" not found
E0225 13:15:03.940813       1 target_config_reconciler.go:87] "unable to get operator configuration" err="secondaryschedulers.operator.openshift.io \"secondary-scheduler\" not found" namespace="openshift-secondary-scheduler-operator" secondary-scheduler="secondary-scheduler"
E0225 13:15:03.940826       1 target_config_reconciler.go:278] key failed with : secondaryschedulers.operator.openshift.io "secondary-scheduler" not found
E0225 13:23:18.834703       1 target_config_reconciler.go:87] "unable to get operator configuration" err="secondaryschedulers.operator.openshift.io \"secondary-scheduler\" not found" namespace="openshift-secondary-scheduler-operator" secondary-scheduler="secondary-scheduler"

[knarra@knarra test]$ oc get pods -n openshift-secondary-scheduler-operator
NAME                                           READY   STATUS    RESTARTS   AGE
secondary-scheduler-operator-d8488677d-2k9sj   1/1     Running   0          5h33m


Expected results:
should be able to create SecondaryScheduler instance

Additional info:
Comment 2 RamaKasturi 2022-03-03 10:10:07 UTC 
Verified with the latest SSO operator and cannot see that error now. The CR instance is named as 'cluster' instead of secondary-scheduler. Based on this moving bug to verified state.
Comment 4 errata-xmlrpc 2022-08-10 10:51:23 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 (Important: OpenShift Container Platform 4.11.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-2022:5069