Bug 1813902 - [UI][Operator] Position of "Update Channel" should be prior to "Installation Mode" when Create Operator Subscription from UI.
Summary: [UI][Operator] Position of "Update Channel" should be prior to "Installation ...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.4.z
Assignee: Cyril
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On: 1791657
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-16 13:01 UTC by Robb Hamilton
Modified: 2020-06-18 18:42 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1791657
Environment:
Last Closed: 2020-06-18 18:42:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Robb Hamilton 2020-03-16 13:01:13 UTC
+++ This bug was initially created as a clone of Bug #1791657 +++

Description of problem:
OperatorHub > Operator Subscription > Create Operator Subscription on the web, is prior to "Update Channel" now, take local storage operator for example. it can only be installed in specific namespace, after choosing the expected namespace, then if "update channel" need to be modified, the "Installation Mode" will be back to the default option(all namespace). 
Also from the configuration side, "Update Channel" has a higher level than "Installation Mode"

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

How reproducible:
Always

Steps to Reproduce:
See Description.

Actual results:
"Installation Mode" is prior to "Update Channel"

Expected results:
"Update Channel" is prior to "Installation Mode"

Additional info:
Comments from jiazha: the "Installation Mode" definiation located in the CSV file, and the "Update Channel"s in the package file which located in the parent folder. So, for me, I think the first step should be choosing the Channel.

Comment 1 Scott Dodson 2020-04-24 13:07:58 UTC
This is target release 4.4.0 bug Severity low, those two seem incompatible so I'm moving this to 4.4.z to get it off of the GA blocker list.

Comment 2 Yadan Pei 2020-05-12 01:56:00 UTC
Both PR are still open, change to MODIFIED

Comment 5 Yanping Zhang 2020-05-17 08:21:03 UTC
PRs for the bug are not merged.


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