Bug 1697333

Summary: VM wizard doesn't verify if VM with entered name already exists and gets stuck on creating VM
Product: Container Native Virtualization (CNV) Reporter: Radim Hrazdil <rhrazdil>
Component: User ExperienceAssignee: Phillip Bailey <phbailey>
Status: CLOSED ERRATA QA Contact: Radim Hrazdil <rhrazdil>
Severity: high Docs Contact:
Priority: high    
Version: 2.0CC: cnv-qe-bugs, mgoldboi, ncredi, rawagner
Target Milestone: ---   
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.0.0-14.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-24 20:15:51 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:
Attachments:
Description Flags
validation screenshot none

Description Radim Hrazdil 2019-04-08 11:36:47 UTC 
Description of problem:
VM wizard doesn't verify if VM with entered name already exists. There should be a check consistent with 'Clone VM' dialog where we check if VM with entered name exists in given namespace. If VM already exists, display help box and don't let user proceed.


Version-Release number of selected component (if applicable):
kubevirt-web-ui:v2.0.0-4.1

How reproducible:
100%

Steps to Reproduce:
1. Create a VM called 'test'
2. Create another VM called 'test' in the same namespace
3.

Actual results:
Wizard is stuck on 'Creation of VM in progress'

Expected results:
Wizard should verify entered name and don't let user proceed

Additional info:
Comment 1 Radim Hrazdil 2019-05-21 12:18:47 UTC 
Verified that VM wizard checks if VM with given name already exists.
Version 2.0.0-14.5
Comment 2 Radim Hrazdil 2019-05-21 12:19:42 UTC 
Created attachment 1571599 [details]
validation screenshot
Comment 4 errata-xmlrpc 2019-07-24 20:15:51 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