Bug 1714004

Summary:	[V2V] [UI] New connection to VMWare is not saved after all details were provided
Product:	Container Native Virtualization (CNV)	Reporter:	Igor Braginsky <ibragins>
Component:	User Experience	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED ERRATA	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.0	CC:	cnv-qe-bugs, istein, mlibra, ncredi, sgordon, tjelinek
Target Milestone:	---	Keywords:	UserExperience
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kubevirt-web-ui:v2.0.0-14.7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-24 20:16:06 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 Igor Braginsky 2019-05-26 13:57:37 UTC

Description of problem:
New connection to VMWare is not saved after all details were provided if import process didn't succeed.

Version-Release number of selected component (if applicable):
v2.0.0-18

How reproducible: 100%


Steps to Reproduce:
1. Open wizard of "Create Virtual Machine"
2. select "Provision source" - import => VMWare => New connection
3. Specify all details of connection
4. Check "Remember vCenter credentials" checkbox
5. Press "Check" button

Actual results:
Connection is not saved if wizard was not completed or failed

Expected results:
Connection is saved and can be used in future even if wizard was not completed (or wizard was cancelled or import failed)

Additional info:

Comment 1 Nelly Credi 2019-05-27 11:47:40 UTC

setting to high as since we dont have bulk import, this is really a bad customer experience

Comment 4 Ilanit Stein 2019-06-20 13:22:57 UTC

Verified on hco-bundle-registry:v2.0.0-27.

For CNV that had a VMware provider saved already - Removed it's details from the saved Secrets,
and then run a v2v migration for a VM with disk, larger than available pvs.

The VM import failed (on that there are no available nodes), as expected.
and when opening the Create VM wizard, with chossing import, and VMware provider, show that the VMware provider details were saved, from previous v2v trial.

Comment 6 errata-xmlrpc 2019-07-24 20:16:06 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-2019:1850