Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1851798

Summary: "Container-native virtualization" or "OpenShift virtualization" displayed in Operator Hub randomly.
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, cnv-qe-bugs, gouyang, jokerman, ncredi, pweil, spadgett, stirabos, tjelinek, yzamir
Target Milestone: ---Keywords: Reopened
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-07-07 14:47:16 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
cnv virt
none
openshift virt
none
openshift virtualization in operatorHub none

Description Guohua Ouyang 2020-06-29 02:38:17 UTC
Created attachment 1699068 [details]
cnv virt

Description of problem:
Go to OperatorHub -> Installed, the installed operator is "Container-native virtualization" 2.3.0 at some time, and sometimes is "OpenShift virtualization" 2.4.0.

Version-Release number of selected component (if applicable):
4.5.0-rc.4

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Guohua Ouyang 2020-06-29 02:39:05 UTC
Created attachment 1699069 [details]
openshift virt

Comment 2 Yaacov Zamir 2020-06-29 09:03:01 UTC
@Tomas hi, It doesn't think kubevirt plugin can help here, do you know what component this belongs to ?

Comment 3 Tomas Jelinek 2020-07-01 07:40:33 UTC
I would guess installation.

Comment 4 Guohua Ouyang 2020-07-01 09:03:26 UTC
If it's not reproduced, try these steps:
1. uninstall hco and OpenShift virtualization operator.
2. reinstall them.
3. check OperatorHub -> Installed

Comment 5 Simone Tiraboschi 2020-07-01 12:10:59 UTC
This on my opinion is really really close to https://bugzilla.redhat.com/show_bug.cgi?id=1844588

As you can image we have more than one CSV in the bundle for the upgrade time.
At 2.3 time the product was called "Container-native virtualization" while now on 2.4 (the default OLM channel in this release) it's called "OpenShift virtualization"

I fear that OperatorHub UI is currently displaying the name from the CSV in the default channel in one page and just a random one in another page as for the logo in https://bugzilla.redhat.com/show_bug.cgi?id=1844588

Moving to Management Console for further investigation

Comment 6 Nelly Credi 2020-07-01 12:35:43 UTC
potentially this will be fixed with the fix of https://bugzilla.redhat.com/show_bug.cgi?id=1846194

Comment 7 Samuel Padgett 2020-07-01 15:30:58 UTC
> At 2.3 time the product was called "Container-native virtualization" while now on 2.4 (the default OLM channel in this release) it's called "OpenShift virtualization"

This is working as intended. Different versions of the operator have different names. We show the name from the installed version in the Installed Operators. In OperatorHub, we show the name of the default channel (since you haven't picked a channel yet).

I'm not sure what else console can really do if different channels have different names.


> I fear that OperatorHub UI is currently displaying the name from the CSV in the default channel in one page and just a random one in another page as for the logo in https://bugzilla.redhat.com/show_bug.cgi?id=1844588

We're not showing a random one. We're showing the value for the actual installed channel once you install the operator.

Comment 8 Guohua Ouyang 2020-07-02 01:23:17 UTC
(In reply to Samuel Padgett from comment #7)
> > At 2.3 time the product was called "Container-native virtualization" while now on 2.4 (the default OLM channel in this release) it's called "OpenShift virtualization"
> 
> This is working as intended. Different versions of the operator have
> different names. We show the name from the installed version in the
> Installed Operators. In OperatorHub, we show the name of the default channel
> (since you haven't picked a channel yet).
> 
This bug is a bit difference from bug 1846194 though it maybe fixed by it.
The problem is under OperatorHub -> Installed, it shows two logo randomly, sometimes it's "Container-native virtualization/2.3.0" and sometimes it is "OpenShift virtualization/2.4.0". 
> I'm not sure what else console can really do if different channels have
> different names.
> 
> 
> > I fear that OperatorHub UI is currently displaying the name from the CSV in the default channel in one page and just a random one in another page as for the logo in https://bugzilla.redhat.com/show_bug.cgi?id=1844588
> 
> We're not showing a random one. We're showing the value for the actual
> installed channel once you install the operator.

Comment 9 Samuel Padgett 2020-07-02 16:10:49 UTC
Hi, can you give us precise steps to reproduce and explain what you see and what you expect to see? Without this, it's hard for us to know what the bug is.

Comment 10 Guohua Ouyang 2020-07-03 02:31:02 UTC
Created attachment 1699762 [details]
openshift virtualization in operatorHub

Upload a video to show the "Container-native virtualization" or "OpenShift virtualization" displayed alternatively.

Steps:
1. navigate to operatorHub -> installed, it's "Container-native virtualization".
2. navigate to other place. 
3. navigate to operatorHub -> installed, it's "OpenShift virtualization".

Expected results: it should always be "OpenShift virtualization".

Comment 13 Samuel Padgett 2020-07-07 14:47:16 UTC
After getting access to the cluster with the issue, I've confirmed you have the same operator with the same name in different catalog sources. This is a duplicate of bug 1814822.

*** This bug has been marked as a duplicate of bug 1814822 ***