Bug 1845061 - Version displayed in Container Native Virtualization OperatorHub side panel
Summary: Version displayed in Container Native Virtualization OperatorHub side panel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 2.4.0
Assignee: Simone Tiraboschi
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-08 11:42 UTC by Radim Hrazdil
Modified: 2020-07-28 19:10 UTC (History)
3 users (show)

Fixed In Version: hco-bundle-registry-container-v2.3.0-303
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-28 19:10:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (555.42 KB, image/png)
2020-06-08 11:42 UTC, Radim Hrazdil
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:3194 0 None None None 2020-07-28 19:10:43 UTC

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


Note You need to log in before you can comment on or make changes to this bug.