Bug 1384204

Summary: Service : GCE service catalog request fails because of VM name regex constraint
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvisioningAssignee: Lucy Fu <lufu>
Status: CLOSED ERRATA QA Contact: Shveta <sshveta>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: cpelland, jhardy, obarenbo
Target Milestone: GA   
Target Release: 5.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: service:google
Fixed In Version: 5.7.0.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1379476 Environment:
Last Closed: 2017-01-04 13:02:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: GCE Target Upstream Version:
Embargoed:
Bug Depends On: 1379476    
Bug Blocks:    

Comment 3 CFME Bot 2016-10-17 16:20:31 UTC
New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/1f9a8af060480894a72399200ee4116d282f03ae

commit 1f9a8af060480894a72399200ee4116d282f03ae
Author:     Greg McCullough <gmccullo>
AuthorDate: Thu Oct 6 12:06:15 2016 -0400
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Thu Oct 13 15:11:36 2016 -0400

    Merge pull request #11745 from lfu/name_service_template_1379476
    
    Stop appending the "_" character as part of the enforced VM naming.
    (cherry picked from commit fd8b6020731da1cd145b1ae5aa2293d24f8d5117)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1384204

 app/models/miq_provision/naming.rb                      |  1 -
 .../providers/vmware/infra_manager/provision_spec.rb    | 17 +++++++++++++++++
 spec/models/miq_provision_request_template_spec.rb      |  4 ++--
 3 files changed, 19 insertions(+), 3 deletions(-)

Comment 4 Shveta 2016-10-19 00:40:30 UTC
Fixed.
Verified in 5.7.0.5-alpha2.20161014143521_cd366b6

Comment 6 errata-xmlrpc 2017-01-04 13:02:53 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://rhn.redhat.com/errata/RHBA-2017-0012.html