Bug 1913821

Summary:	Need definitive steps about uninstalling descheduler operator
Product:	OpenShift Container Platform	Reporter:	RamaKasturi <knarra>
Component:	kube-scheduler	Assignee:	Jan Chaloupka <jchaloup>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.7	CC:	aos-bugs, mfojtik
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:50:58 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 2021-01-07 16:55:24 UTC

Description of problem:
Currently uninstalling of descheduler operator is being performed from UI and we do not have definitive /documented steps to do it. With the current way we see cluster pod not getting deleted/removed even after uninstalling descheduler operator.

current flow is : login to UI, clickInstalledOperators -> Click KubeDeschedulerOperator -> Click KubeDescheduler -> click three dots -> delete kubedescheduler -> Click Uninstall Operator -> Click Namespace -> select cluster-kube-descheduler-operator -> click delete -> confirm the namespace name by typing in again.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jan Chaloupka 2021-01-11 18:06:12 UTC

Right after "delete kubedescheduler" step, operator logs are complaining about:
```
E0111 17:57:44.723928       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"
```

So once kubedescheduler/cluster object is gone, operator can't do anothing about existing descheduler deployment.

Comment 2 Jan Chaloupka 2021-01-15 11:06:40 UTC

In case the PR does get merged today, setting UpcomingSprint

Comment 4 RamaKasturi 2021-01-25 10:27:18 UTC

Below are the steps used to uninstall a descheduler operator and they work fine.

[knarra@knarra ~]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-01-21-215614   True        False         4h      Cluster version is 4.7.0-0.nightly-2021-01-21-215614

[knarra@knarra ~]$ oc get csv -n openshift-kube-descheduler-operator
NAME                                                   DISPLAY                     VERSION                 REPLACES   PHASE
clusterkubedescheduleroperator.4.7.0-202101230053.p0   Kube Descheduler Operator   4.7.0-202101230053.p0              Succeeded


1) Browse console weburl
2) Delete the kubeDescheduler cluster object
3) Uninstall descheduler operator
4) Delete cluster-kube-descheduler namespace
5) Delete kubedescheduler custom resource definition.

After performing the above steps tried to install descheduler again and it worked fine.

Based on the above moving bug to verified state.

Comment 7 errata-xmlrpc 2021-02-24 15:50:58 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.7.0 security, bug fix, and enhancement 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-2020:5633