Bug 1871232

Summary: [DeScheduler] - UI shows two descheduler operators both provided by RedHat
Product: OpenShift Container Platform Reporter: RamaKasturi <knarra>
Component: kube-schedulerAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: low Docs Contact:
Priority: low    
Version: 4.6CC: aos-bugs, jchaloup, maszulik, mfojtik
Target Milestone: ---   
Target Release: 4.6.0   
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: 2020-10-27 16:30:38 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:
Attachments:
Description Flags
Descheduler image overview in console
none
Attaching the screenshot with fix none

Description RamaKasturi 2020-08-21 17:18:38 UTC
Description of problem:
When trying to install descheduler from UI i see that it lists two operators both reads Provided by RedHat where as one of them is a community operator and other one is provided by RedHat. This might create confusion to end users on what they are supposed to install since both the operators have provided Red Hat, either we needed to remove provided by Red Hat label or move back to the old way where two operator gets displayed and one of them says "community operator"

Version-Release number of selected component (if applicable):
[ramakasturinarra@dhcp35-60 ~]$ oc get csv
NAME                                                   DISPLAY                     VERSION                 REPLACES   PHASE
clusterkubedescheduleroperator.4.6.0-202008200527.p0   Kube Descheduler Operator   4.6.0-202008200527.p0              Succeeded
[ramakasturinarra@dhcp35-60 ~]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.6.0-0.nightly-2020-08-21-011653   True        False         10h     Cluster version is 4.6.0-0.nightly-2020-08-21-011653


How reproducible:
Always

Steps to Reproduce:
1. Install 4.6 cluster
2. Browse through UI
3. search for descheduler

Actual results:
User will see two operators one named descheduler (provided by RedHat) another one named kube-descheduler-operator (provided by RedHat Inc)

Expected results:
User should either see one of them, or the community operator should not show that it is provided by RedHat.

Additional info:
Attaching screenshot for the same for reference.

Comment 1 RamaKasturi 2020-08-21 17:19:09 UTC
Created attachment 1712204 [details]
Descheduler image overview in console

Comment 2 Maciej Szulik 2020-08-21 17:43:41 UTC
Jan can this be the old one that's showing up?

Comment 3 Jan Chaloupka 2020-08-24 11:57:47 UTC
Yeah, the old one is still present

Comment 4 Jan Chaloupka 2020-09-01 14:25:51 UTC
https://github.com/operator-framework/community-operators/pull/2243 for either dropping the old operator or figuring out another solution how to deprecate it

Comment 5 Jan Chaloupka 2020-09-10 14:18:49 UTC
The PR is merged upstream. Moving to QA to check if the old operator is gone or still appears in the console.

Comment 6 RamaKasturi 2020-09-16 13:30:32 UTC
Verified with the latest payload and i can see only one operator, based on that moving the bug to verified state.

[ramakasturinarra@dhcp35-60 openshift-client-linux-4.6.0-0.nightly-2020-09-16-000734]$ oc version
Client Version: 4.6.0-202009160247.p0-0d989c3
Server Version: 4.6.0-0.nightly-2020-09-15-045818
Kubernetes Version: v1.19.0+35ab7c5

Attaching the screenshot for reference, moving bug to verified based on this.

Comment 7 RamaKasturi 2020-09-16 13:31:34 UTC
Created attachment 1715087 [details]
Attaching the screenshot with fix

Comment 10 errata-xmlrpc 2020-10-27 16:30:38 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.6 GA Images), 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-2020:4196