Bug 1797252 - CNV 2.2 Operator includes an empty 2.3 update channel
Summary: CNV 2.2 Operator includes an empty 2.3 update channel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 2.2.0
Assignee: Simone Tiraboschi
QA Contact: Irina Gulina
URL:
Whiteboard:
Depends On:
Blocks: 1797804
TreeView+ depends on / blocked
 
Reported: 2020-02-01 21:19 UTC by Stephen Gordon
Modified: 2020-05-28 09:42 UTC (History)
6 users (show)

Fixed In Version: hco-bundle-registry-container-v2.2.0-312
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-12 12:25:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Provided by KubeVirt project. (70.70 KB, image/png)
2020-02-01 21:19 UTC, Stephen Gordon
no flags Details
Operator details view. (111.02 KB, image/png)
2020-02-01 21:20 UTC, Stephen Gordon
no flags Details
Operator subscription view (144.47 KB, image/png)
2020-02-01 21:21 UTC, Stephen Gordon
no flags Details
'Create Operator Subscription' screenshot - Fixed (53.15 KB, image/png)
2020-02-10 13:13 UTC, Israel Pinto
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0480 0 None None None 2020-02-12 12:26:02 UTC

Description Stephen Gordon 2020-02-01 21:19:28 UTC
Created attachment 1657053 [details]
Provided by KubeVirt project.

Description of problem:

Installed CNV 2.2 and OCP 4.3 and noticed a few oddities in the process.

Version-Release number of selected component (if applicable):

OCP 4.3
CNV 2.2

How reproducible:

100%

Actual results:

1. When searching operator hub only one operator comes up (good) - "Container-native virtualization", but the subhead says it's "provided by KubeVirt project".

2. Details screen after clicking the operator also says the provider is the KubeVirt project.

3. Create operator subscription screen has a 2.3 update channel, but 2.3 isn't meant to be public/released?

Expected results:

1. Should say "provided by Red Hat"
2. 2.3 update channel should not be available at this time.

Additional info:

Screenshots attached.

Comment 1 Stephen Gordon 2020-02-01 21:20:38 UTC
Created attachment 1657054 [details]
Operator details view.

Comment 2 Stephen Gordon 2020-02-01 21:21:17 UTC
Created attachment 1657055 [details]
Operator subscription view

Comment 3 Simone Tiraboschi 2020-02-07 08:52:45 UTC
"provided by KubeVirt" and other fields (keywords, links...) are already fixed for 2.3 but we never backported the fix to the unified CSV generator to 2.2 because we were already in blockers only mode.

2.3 channel is basically empty (the images are not there because they weren't attached to 2.2.0 errata) but the channel is visible because we want it staging, for testability reasons, but we don't have any mechanism to ignore it moving from staging to prod.
Technically the user can simply edit the subscription choosing the right channel and the install process will start.

On the other side, this is causing other serious troubles such as 1797804 where `oc adm catalog build` fails mirroring the whole catalog is just one of the images is missing (as with an empty channel as in this case).

The only option now is an async errata just with the bundle image where we *manually* remove 2.3 channel and ensure that everything else is kept untouched.
This is basically just a manual, and possibly error prone hack, but we definitively a kind of automatic mechanism for this on RCM side for the future.

Comment 8 Israel Pinto 2020-02-10 13:13:13 UTC
Created attachment 1662138 [details]
'Create Operator Subscription' screenshot - Fixed

Comment 9 Nelly Credi 2020-02-11 17:45:03 UTC
We were able to deploy and we do not see 2.3 anymore
The OCP bug was also verified, so the issue is fixed from their side as well

Comment 11 errata-xmlrpc 2020-02-12 12:25:56 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/RHBA-2020:0480

Comment 12 Simone Tiraboschi 2020-05-28 09:42:03 UTC
Removing old need info.


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