Bug 1376520 – service template provision tasks failing in check provision method

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1376520 - service template provision tasks failing in check provision method

Summary:	service template provision tasks failing in check provision method

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	Provisioning (Show other bugs)
Sub Component:
Version:	5.6.0
Hardware:	All All

Priority	urgent Severity urgent
Target Milestone:	GA
Target Release:	5.6.2
Assigned To:	Bill Wei
QA Contact:	Milan Falešník
Docs Contact:

URL:
Whiteboard:	service:provision
Keywords:	ZStream

Depends On:	1374060
Blocks:
	Show dependency tree / graph

Reported:	2016-09-15 12:05 EDT by Satoe Imaishi
Modified:	2016-10-04 10:39 EDT (History)
CC List:	5 users (show)

See Also:
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 10:39:38 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Unknown

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2016:1996	normal	SHIPPED_LIVE	Important: CFME 4.1 bug fixes and enhancement update	2016-10-04 14:26:13 EDT

Groups: None (edit)

Comment 2 Bill Wei 2016-09-19 15:46:04 EDT

darga/yes
https://github.com/ManageIQ/manageiq/pull/11203

Comment 3 Oleg Barenboim 2016-09-20 15:31:09 EDT

Darga PR https://github.com/ManageIQ/manageiq/pull/11404 has been merged

Comment 5 Bill Wei 2016-09-23 09:20:18 EDT

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 12:24:46 EDT

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 10:39:38 EDT

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

Note You need to log in before you can comment on or make changes to this bug.