Bug 1974414
| Summary: | Uninstalling kube-descheduler clusterkubedescheduleroperator.4.6.0-202106010807.p0.git.5db84c5 removes some clusterrolebindings | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Vu Dinh <vdinh> |
| Component: | OLM | Assignee: | Vu Dinh <vdinh> |
| OLM sub component: | OLM | QA Contact: | RamaKasturi <knarra> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | cldavey, knarra, openshift-bugs-escalate, xiuwang |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.8.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-27 23:13:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1970910 | ||
| Bug Blocks: | 1975453 | ||
|
Description
Vu Dinh
2021-06-21 15:43:52 UTC
Hello Vu Dinh, one question related to the bug here, do we need to try with the same version of descheduler you provided at [1] on 4.8 cluster as well ? Also after deleting the csv i do not see any clusterrolebindings of the namespaces are deleted. [1] docker.io/dinhxuanvu/descheduler-index:v1 Thanks kasturi Hey Rama, Yes, please use the same version for descheduler operator. Vu Moving the bug to verified state as i did not see any CRB getting deleted after deletion of csv. Below are the steps i followed to verify the bug.
steps followed:
===================
1) Install latest 4.8 cluster
2) create namespace called 'openshift-kube-descheduler-operator'
3) create operatorgroup using the yaml below
[knarra@knarra ~]$ cat /tmp/operatorgroup.yaml
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
name: openshift-kube-descheduler-operator
namespace: openshift-kube-descheduler-operator
spec:
targetNamespaces:
- openshift-kube-descheduler-operator
4) create catalogsource with index image using the yaml below
[knarra@knarra ~]$ cat /tmp/catalogsource.yaml
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: qe-app-registry
namespace: openshift-kube-descheduler-operator
spec:
sourceType: grpc
image: docker.io/dinhxuanvu/descheduler-index:v1
5) create subscription using the yaml file below
[knarra@knarra ~]$ cat /tmp/subscription.yaml
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: cluster-kube-descheduler-operator
namespace: openshift-kube-descheduler-operator
spec:
channel: stable
name: cluster-kube-descheduler-operator
source: qe-app-registry
sourceNamespace: openshift-kube-descheduler-operator
Now you can see that csv is in pending state with error "one or more requirements could not be found"
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal RequirementsUnknown 2m15s operator-lifecycle-manager requirements not yet checked
Normal RequirementsNotMet 2m14s (x2 over 2m15s) operator-lifecycle-manager one or more requirements couldn't be found
[knarra@knarra ~]$ oc get clusterrolebinding -A | wc -l
200
[knarra@knarra ~]$ oc get csv
NAME DISPLAY VERSION REPLACES PHASE
clusterkubedescheduleroperator.4.6.0-202106010807.p0.git.5db84c5 Kube Descheduler Operator 4.6.0-202106010807.p0.git.5db84c5 Pending
[knarra@knarra ~]$ oc delete csv clusterkubedescheduleroperator.4.6.0-202106010807.p0.git.5db84c5
clusterserviceversion.operators.coreos.com "clusterkubedescheduleroperator.4.6.0-202106010807.p0.git.5db84c5" deleted
[knarra@knarra ~]$ oc get clusterrolebinding -A | wc -l
200
[knarra@knarra ~]$ oc get clusterrolebinding -A | wc -l
200
[knarra@knarra ~]$ oc get clusterrolebinding -A | wc -l
200
If this bug target release version should be set 4.8.0? Seems the bug is verified on 4.8.0 version Hello XiuJuan, I am not sure if the target version should be set to 4.8.0, this bug was created just for the backporting purpose to 4.6. This was a bug which was seen in ocp4.6 and customer needed a fix as he is not willing to upgrade to 4.7. So we had to backport all the way from 4.9 to 4.6 though this issue does not appear on ocp4.7+. May be Vu Dinh will be a good contact to see if we can set the targetRelease to 4.8.0 ? Thanks kasturi 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.8.2 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-2021:2438 |