Bug 1840749 - [UI] RHV to CNV import wizard: "Select RHV Instance Secret" should be "Select RHV Instance"
Summary: [UI] RHV to CNV import wizard: "Select RHV Instance Secret" should be "Select...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Filip Krepinsky
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2020-05-27 14:30 UTC by Avital Pinnick
Modified: 2020-07-13 17:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2020-07-13 17:42:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
RHV "Connect to Provider" screen (163.11 KB, image/png)
2020-05-27 14:30 UTC, Avital Pinnick
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 5604 0 None closed Bug 1840749: make RHV Instance naming consistent in VM Import Wizard 2020-06-24 03:27:27 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:42:26 UTC

Description Avital Pinnick 2020-05-27 14:30:55 UTC
Created attachment 1692718 [details]
RHV "Connect to Provider" screen

In the "Connect to Provider" screen of the "Import VM" wizard, the default value of the "RHV Instance" dropdown list is "Select RHV Instance Secret."

The default value should be "Select RHV Instance". This wording is consistent with VMware import wizard. 

Although RHV instances are saved as secrets, the user will either select "Connect to New Instance" (= creating an instance secret that does not yet exist) or a saved RHV instance (= secret). The user does not need to know that connecting to a saved instance uses a saved secret. As far as the user is concerned, the choices are connecting to a new instance or a saved instance.

Comment 4 Radim Hrazdil 2020-05-28 10:59:13 UTC

Comment 5 errata-xmlrpc 2020-07-13 17:42:09 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.


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