Bug 1845061

Summary: Version displayed in Container Native Virtualization OperatorHub side panel
Product: Container Native Virtualization (CNV) Reporter: Radim Hrazdil <rhrazdil>
Component: InstallationAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED ERRATA QA Contact: Radim Hrazdil <rhrazdil>
Severity: low Docs Contact:
Priority: low    
Version: 2.4.0CC: cnv-qe-bugs, ncredi, stirabos
Target Milestone: ---   
Target Release: 2.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hco-bundle-registry-container-v2.3.0-303 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-28 19:10:31 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
screenshot none

Description Radim Hrazdil 2020-06-08 11:42:33 UTC
Created attachment 1696042 [details]
screenshot

Description of problem:
When a user opens CNV Operator side panel in OperatorHub (see screenshot), there is  
'Operator Version' 2.3.1.
But when the user clicks Install button, one can select from channels 
2.1, 2.2, 2.3, 2.4 and alpha.

I'm wondering, what is the purpose of displaying the 2.3.1 Version?
Does it make sense to display it when the user can select channel in the next step?
I think that this may cause confusion to people who intent to install different version that happens to be displayed on the Operator side panel overview.


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


How reproducible:
100%

Steps to Reproduce:
1. Navigate to OperatorHub
2. Search container-native
3. click the found container native Operator item

Comment 5 errata-xmlrpc 2020-07-28 19:10:31 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, 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:3194