Bug 1377889

Summary: Azure : Instance name restriction should be shown in UI when deploying template for Azure
Product: Red Hat CloudForms Management Engine Reporter: Shveta <sshveta>
Component: ProvidersAssignee: Daniel Berger <dberger>
Status: CLOSED CURRENTRELEASE QA Contact: Jeff Teehan <jteehan>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: cpelland, dberger, dclarizi, hkataria, jfrey, jhardy, jteehan, mpovolny, obarenbo, simaishi
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: provider:ui:azure
Fixed In Version: 5.8.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1402528 (view as bug list) Environment:
Last Closed: 2017-06-12 16:36:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Feature
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Azure Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1402528    

Description Shveta 2016-09-20 22:41:57 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Create a catalog item for Azure 
2. if the Instance name provided is more than 15 chars or has special chars ,the request fails.
3. It will be good to show this restriction while creating the item

Actual results:


Expected results:


Additional info:
Comment 3 Jeff Teehan 2016-10-04 23:48:29 UTC 
I'll take this one too.  Especially since the rules keep changing.
Comment 7 Daniel Berger 2016-12-01 18:02:18 UTC 
https://github.com/ManageIQ/manageiq/pull/12947
Comment 8 Jeff Teehan 2016-12-01 18:29:06 UTC 
Added new test case id above - I'm checking the 1 character vm name now.
Comment 10 Jeff Teehan 2017-04-26 17:32:57 UTC 
This bug is the same as the password bug, which is to say it's two bugs.  One is fixed in basic lifecycle provision, this one, but another bug needs to be fixed for the azure provision template JSON.
Comment 11 Jeff Teehan 2017-04-27 17:47:08 UTC 
I'm going to rename these and move them to verified.  Then open up a consolidate bug for Bill to update the template with these validations.  There should have been two bugs for this issue, but since Dan already submitted commits to fix the none-orchestration UI.

This is working otherwise when LifeCycle deploying templates.