This bug was initially created as a copy of Bug #1845031
I am copying this bug because:
Description of problem:
When user procieeds installation steps for CNV Operator from 2.4 channel, the namespace openshift-cnv is not created automatically.
When namespace openshift-cnv is created before the installation, it isn't used when user navigates to the OperatorHub from a different namespace (for example, openshift-cnv ns is created with CLI, user is currently in Default namespace in the UI and navigates to Operator Hub to install CNV Operator). Instead, the last active namespace is used (In the previous example, it would be Default).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make sure openshift-cnv namespace doesn't exist
2. Navigate to OperatorHub, search container-native, click install, select 2.4 channel, click install
1) Create openshift-cnv namespace
2) Switch to 'Default' project
3) Navigate to OperatorHub, search container-native, click install, select 2.4 channel, click install
the Openshift Virtualization operator is deployed to the last active namespace, not openshift-cnv
a) openshift-cnv namespace should be created for the user
b) when openshift-cnv namespace exists, it should be used instead of the least recently used namespace
it shouldn't matter from which namespace the user navigates to the operatorHub
Waiting to dependent bug gets Verified. Adding UpcomingSprint to have it reevaluated in the next cycle.
*** Bug 1845639 has been marked as a duplicate of this bug. ***
Created attachment 1702163 [details]
verification screenshot for scenario B
Scenario a) Namespace created successfully together with the operator
Scenario b) Browsed to Default namespace and created the operator successfully automatically under openshift-cnv (attached the screen recording for refer)
This could be verified on 4.5.0-0.nightly-2020-07-23-023500
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.