Description of problem: I see that deleting secondaryscheduler CR does not delete the corresponding deployment. Version-Release number of selected component (if applicable): secondaryscheduleroperator.v1.1.0 How reproducible: always Steps to Reproduce: 1. Install secondary scheduler operator on ocp4.11 2. Now from the UI delete the secondaryscheduler CR 3. Actual results: we can see that the secondary scheduler pod still runs and the deployment is not gone. [knarra@knarra OpenShift]$ oc get pods -n openshift-secondary-scheduler-operator NAME READY STATUS RESTARTS AGE secondary-scheduler-5c67b4949f-lbwbr 1/1 Running 0 6m54s secondary-scheduler-operator-587b79f464-pm4bs 1/1 Running 0 7m35s [knarra@knarra OpenShift]$ oc get deployment -n openshift-secondary-scheduler-operator NAME READY UP-TO-DATE AVAILABLE AGE secondary-scheduler 1/1 1 1 5m18s secondary-scheduler-operator 1/1 1 1 5m59s Expected results: When secondaryscheduler CR is deleted it should delete its deployment Additional info:
Moving the bug to verified state as i see that when secondary scheduler CR gets deleted it does delete the corresponding deployment. [knarra@knarra ~]$ oc get csv -n openshift-secondary-scheduler-operator NAME DISPLAY VERSION REPLACES PHASE secondaryscheduleroperator.v1.1.0 Secondary Scheduler Operator for Red Hat OpenShift 1.1.0 Succeeded [knarra@knarra ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-rc.1 True False 3h30m Cluster version is 4.11.0-rc.1 [knarra@knarra ~]$ oc get deployment -n openshift-secondary-scheduler-operator NAME READY UP-TO-DATE AVAILABLE AGE secondary-scheduler 1/1 1 1 8m33s secondary-scheduler-operator 1/1 1 1 9m19s [knarra@knarra ~]$ oc get pods -n openshift-secondary-scheduler-operator NAME READY STATUS RESTARTS AGE secondary-scheduler-685d5ccbff-xtdg2 1/1 Terminating 0 8m51s secondary-scheduler-operator-779cd6cc46-b99ls 1/1 Running 0 9m37s [knarra@knarra ~]$ oc get pods -n openshift-secondary-scheduler-operator NAME READY STATUS RESTARTS AGE secondary-scheduler-685d5ccbff-xtdg2 1/1 Terminating 0 8m54s secondary-scheduler-operator-779cd6cc46-b99ls 1/1 Running 0 9m40s [knarra@knarra ~]$ oc get pods -n openshift-secondary-scheduler-operator NAME READY STATUS RESTARTS AGE secondary-scheduler-685d5ccbff-xtdg2 1/1 Terminating 0 8m56s secondary-scheduler-operator-779cd6cc46-b99ls 1/1 Running 0 9m42s [knarra@knarra ~]$ oc get pods -n openshift-secondary-scheduler-operator NAME READY STATUS RESTARTS AGE secondary-scheduler-685d5ccbff-xtdg2 1/1 Terminating 0 8m59s secondary-scheduler-operator-779cd6cc46-b99ls 1/1 Running 0 9m45s [knarra@knarra ~]$ oc get deployment -n openshift-secondary-scheduler-operator NAME READY UP-TO-DATE AVAILABLE AGE secondary-scheduler-operator 1/1 1 1 9m48s [knarra@knarra ~]$ oc get pods -n openshift-secondary-scheduler-operator NAME READY STATUS RESTARTS AGE secondary-scheduler-685d5ccbff-xtdg2 1/1 Terminating 0 9m5s secondary-scheduler-operator-779cd6cc46-b99ls 1/1 Running 0 9m51s [knarra@knarra ~]$ oc get pods -n openshift-secondary-scheduler-operator NAME READY STATUS RESTARTS AGE secondary-scheduler-operator-779cd6cc46-b99ls 1/1 Running 0 9m56s [knarra@knarra ~]$ oc get deployment -n openshift-secondary-scheduler-operator NAME READY UP-TO-DATE AVAILABLE AGE secondary-scheduler-operator 1/1 1 1 10m 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 (Moderate: OpenShift Container Platform 4.12.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:7399