Bug 1953707

Summary:	cannot upgrade openshift-kube-descheduler from 4.7.2 to latest
Product:	OpenShift Container Platform	Reporter:	RamaKasturi <knarra>
Component:	kube-scheduler	Assignee:	Jan Chaloupka <jchaloup>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.7	CC:	aos-bugs, mfojtik
Target Milestone:	---
Target Release:	4.7.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-05-19 15:16:51 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:	1943224
Bug Blocks:	1995951

Description RamaKasturi 2021-04-26 17:20:08 UTC

This bug was initially created as a copy of Bug #1943224

I am copying this bug because: 



Description of problem:
I tried to upgrade openshift-kube-descheduler from 4.7.2 to latest but i fail to upgrade and upon further investigation it looks like descheduler operator skiprange needs to be updated.
current skipRange is '>=4.3.0-0 < 4.7.0-0 where as it should be >=4.3.0 < 4.7.0

For more info, we could refer to logging one: https://github.com/openshift/cluster-logging-operator/blob/release-4.5/manifests/4.5/cluster-logging.v4.5.0.clusterserviceversion.yaml

Also discussion related to this: https://coreos.slack.com/archives/CH76YSYSC/p1616568447464200

Version-Release number of selected component (if applicable):
[knarra@knarra ~]$ oc get csv -n openshift-kube-descheduler-operator
NAME                                                   DISPLAY                     VERSION                 REPLACES   PHASE
clusterkubedescheduleroperator.4.7.0-202101300133.p0   Kube Descheduler Operator   4.7.0-202101300133.p0              Succeeded


How reproducible:
Always

Steps to Reproduce:
1. Install 4.7.2 cluster
2. Deploy descheduler operator
3. Edit the catalogSource index image and set that to latest 

Actual results:
Could see that operator does not get upgraded to latest version of 4.7.z

Expected results:
Operator should get updated to latest version of 4.7.z

Additional info:

Comment 3 Jan Chaloupka 2021-04-30 12:05:20 UTC

Waiting for cherry-pick-approved label

Comment 5 RamaKasturi 2021-05-11 10:18:38 UTC

Verified bug with the payload below and i see that upgrade is successful.

[knarra@knarra ~]$ oc get csv
NAME                                                   DISPLAY                     VERSION                 REPLACES                                               PHASE
clusterkubedescheduleroperator.4.7.0-202105061841.p0   Kube Descheduler Operator   4.7.0-202105061841.p0   clusterkubedescheduleroperator.4.7.0-202104250659.p0   Succeeded

[knarra@knarra ~]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-05-05-092347   True        False         26h     Cluster version is 4.7.0-0.nightly-2021-05-05-092347


olm.skipRange: >=4.5.0 <4.7.0-202105061841.p0

Based on the above moving bug to verified state.

Comment 8 errata-xmlrpc 2021-05-19 15:16:51 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 (OpenShift Container Platform 4.7.11 bug fix 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/RHBA-2021:1550