Bug 1529056

Summary: VM\Template Name in VM lifecycle operations should be validated before form submission
Product: Red Hat CloudForms Management Engine Reporter: Ilanit Stein <istein>
Component: ProvisioningAssignee: Greg McCullough <gmccullo>
Status: CLOSED CURRENTRELEASE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: cpelland, gblomqui, jfrey, jhardy, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: CFME Core
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-12 19:18:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:

Description Ilanit Stein 2017-12-26 08:00:58 UTC
Description of problem:
For the following VMs & Templates lifecycle operations:

1. "VM provision from a template" 
     - Create a VM named "VM name", from a template. 
2. "Publish VM to a template" 
     - On RHV provider: Create a Template named "Template Name" from a VM. 
     - On other providers: Create a Template, and then create a VM named "VM 
       Name".
3. "Clone Template" 
     - Create a VM named "VM Name" from a Template.

"VM Name"\"Template Name" validation should take place before submitting the request, meaning as part of the dialog.
It is currently done afterwards, at the Request stage.

Version-Release number of selected component (if applicable):
CFME-5.9.0.14

Additional info:
The "VM Name"\"Template Name" fields are located at the VM lifecycle dialogs, under the "Catalog" tab.