Bug 1724973

Summary:	[RFE][v2v] v2v import VM dialog: Use a separate v/x button, for each storage entry
Product:	Container Native Virtualization (CNV)	Reporter:	Ilanit Stein <istein>
Component:	V2V	Assignee:	Brett Thurber <bthurber>
Status:	CLOSED ERRATA	QA Contact:	Igor Braginsky <ibragins>
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.0	CC:	bthurber, cnv-qe-bugs, dagur, ncredi, tjelinek
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	2.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-30 16:27:11 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:

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