Bug 1724973 - [RFE][v2v] v2v import VM dialog: Use a separate v/x button, for each storage entry
Summary: [RFE][v2v] v2v import VM dialog: Use a separate v/x button, for each storage ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: V2V
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 2.2.0
Assignee: Brett Thurber
QA Contact: Igor Braginsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-28 07:51 UTC by Ilanit Stein
Modified: 2020-01-30 16:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-30 16:27:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:0307 0 None None None 2020-01-30 16:27:21 UTC

Description Ilanit Stein 2019-06-28 07:51:06 UTC
Description of problem:
In the create VM with wizard dialog, Storage tab, 

There is a mutual confirmation (v/x) button, that becomes active, once each storage entry is edited.

This is very confusing.

A more reasonable way can be have the x/v button, for each storage entry, so it can be more clear, to which entry it refers. 

Version-Release number of selected component (if applicable):
bundle-registry:v2.0.0-33

Additional info:
https://jira.coreos.com/browse/KNIP-826

Comment 1 Tomas Jelinek 2019-07-31 14:32:49 UTC
This will be addressed in 4.3 timeframe (e.g. cnv 2.2) by changing the VM dialog completely to match the rest of the openshift designs:
https://docs.google.com/document/d/1hsLOjWnFFDdpFFyX6_mMOTFcvuW7lfu9LMpgs3Jzq1M/edit#

I propose to remove this from 2.1, I don't see this happening in time for 2.1.

Comment 3 Igor Braginsky 2019-12-08 08:39:51 UTC
Validated at CNV 2.1.1

Comment 5 errata-xmlrpc 2020-01-30 16:27:11 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/RHEA-2020:0307


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