Bug 1376520

Summary: service template provision tasks failing in check provision method
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvisioningAssignee: Bill Wei <bilwei>
Status: CLOSED ERRATA QA Contact: Milan Falešník <mfalesni>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.6.0CC: bilwei, cpelland, gmccullo, jhardy, obarenbo
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.2   
Hardware: All   
OS: All   
Whiteboard: service:provision
Fixed In Version: 5.6.2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1374060 Environment:
Last Closed: 2016-10-04 14:39:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Unknown Target Upstream Version:
Embargoed:
Bug Depends On: 1374060    
Bug Blocks:    

Comment 2 Bill Wei 2016-09-19 19:46:04 UTC
darga/yes
https://github.com/ManageIQ/manageiq/pull/11203

Comment 3 Oleg Barenboim 2016-09-20 19:31:09 UTC
Darga PR https://github.com/ManageIQ/manageiq/pull/11404 has been merged

Comment 5 Bill Wei 2016-09-23 13:20:18 UTC
This is a general issue although the customer reported with Azure when they ordered the service multiple times simultaneously. There is a timing issue so it may not be easily reproduced. 

You can actually reproduce the error "Stack deployment finished. Status: error, reason: stack has not been deployed" in a simple way. While an orchestration provisioning is running in the "Creating Stack" stage you refresh the same provider manually from the UI.

Comment 6 Milan Falešník 2016-09-30 16:24:46 UTC
Checked in 5.6.2.1.

I was provisioning an orchestration stack service on azure (the canned one), I was trying to refresh the provider all the time but it still worked as expected.

Comment 8 errata-xmlrpc 2016-10-04 14:39:38 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/RHSA-2016-1996.html