Bug 2023675

Summary: Changing CNV Namespace
Product: OpenShift Container Platform Reporter: Kobig <kgershon>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED ERRATA QA Contact: Siva Reddy <schituku>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.8CC: aos-bugs, danken, dmesser, pkreuser, tony.wu, xiyuzhao, yapei
Target Milestone: ---   
Target Release: 4.10.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: 2022-03-10 16:28:41 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:
Bug Depends On:    
Bug Blocks: 2046641    
Attachments:
Description Flags
Non standard name space warning none

Description Kobig 2021-11-16 10:32:03 UTC 
Description of problem:
During CNV Wizard installation (GUI) the namespace for where the CNV can be installed can be edited. This can cause problems with other components that are searching for that Namespace. If we are searching for that NS why do we want to give the option to change it, we should make it hardcoded 


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

How reproducible:
Try to install CNV from the operator hub


Actual results:
The Namespace can be changed/updated

Expected results:
Namespace field should be read-only or not exists 

Additional info:
I think we should show the NS in the GUI but it would be read-only
Comment 1 Jakub Hadvig 2021-11-16 13:56:44 UTC 
Hey Kobig,
so we are preselecting the "Operator recommended Namespace" radio button of the "Install Namespace", in case the operator contains `operatorframework.io/suggested-namespace` annotation, which indicated the recommended namespace to install the operator into.
In this case its `operatorframework.io/suggested-namespace: openshift-cnv`. We cannot force users to user the suggested namespace. 
On the other hand we could add a warning, with message like: "Selected namespace is not recommended for operator installation", if the annotation is present on the operator.

Peter could you please assist here on what the proper fix should look like from the UX side? Thanks !
Comment 2 Peter Kreuser 2021-11-16 14:03:14 UTC 
I believe this 'operator recommended namespace' feature was pretty deliberately implemented to not force the user to select a particular namespace and instead guide the user to the suggested namespace. I've added Daniel Messer and Tony Wu who may have insight as well but I believe this is not a bug.
Comment 3 Kobig 2021-11-16 16:05:52 UTC 
(In reply to Jakub Hadvig from comment #1)
> Hey Kobig,
> so we are preselecting the "Operator recommended Namespace" radio button of
> the "Install Namespace", in case the operator contains
> `operatorframework.io/suggested-namespace` annotation, which indicated the
> recommended namespace to install the operator into.
> In this case its `operatorframework.io/suggested-namespace: openshift-cnv`.
> We cannot force users to user the suggested namespace. 
> On the other hand we could add a warning, with message like: "Selected
> namespace is not recommended for operator installation", if the annotation
> is present on the operator.
> 
> Peter could you please assist here on what the proper fix should look like
> from the UX side? Thanks !

Why cant we force the user to use the Openshift-cnv? 
We have a case(Connected to the BZ and not the first) that NS was changed and it is causing some problems...
Why not prevent issues from happening? and for future operators/features we are all aligned with that NS
Comment 5 Jakub Hadvig 2021-11-17 11:18:54 UTC 
We discussed the fix with Daniel Messer and we will add an waring alert that would notify the user that installing the operator into other then suggested NS can cause problems.
In case further actions are needed please submit and RFE to COnsole or OLM Jira - https://issues.redhat.com/projects/OLM or https://issues.redhat.com/projects/CONSOLE
Comment 7 Dan Kenigsberg 2021-11-22 14:40:14 UTC 
@dmesser typically I'm all for server-side solutions; but here I think the request is just to avoid GUI mistakes:
Let an operator specify something like supportedOnlyOnRecommendedNamespace:true ; then GUI can protect users for falling into an unsupported condition based on this request by disabling the radio button.
Comment 13 Siva Reddy 2022-02-03 22:12:10 UTC 
Created attachment 1858975 [details]
Non standard name space warning


Cluster Version:
  4.10.0-0.nightly-2022-02-02-220834

Steps to verify:
 1. Install a operator and one the wizard try to use another namespace 
     instead of suggested name space

  the error message shows up now.
Comment 15 errata-xmlrpc 2022-03-10 16:28:41 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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-2022:0056