Bug 2100923

Summary:	[SSO] Deleting secondary scheduler CR does not delete the corresponding deployment
Product:	OpenShift Container Platform	Reporter:	RamaKasturi <knarra>
Component:	kube-scheduler	Assignee:	Lucas Severo <lseveroa>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.11	CC:	jchaloup, mfojtik, stevsmit
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	* Previously, the secondary scheduler deployment was not deleted after a secondary scheduler custom resource was deleted. Consequently, the Secondary Schedule Operator and Operand were not fully uninstalled. With this update, the correct owner reference is set in the secondary scheduler custom resource so that it points to the secondary scheduler deployment. As a result, secondary scheduler deployments are deleted when the secondary scheduler custom resource is deleted. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2100923[BZ#2100923])	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-17 19:50:46 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-06-24 17:10:57 UTC

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:

Comment 2 RamaKasturi 2022-07-08 11:27:13 UTC

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.

Comment 5 errata-xmlrpc 2023-01-17 19:50:46 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.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