Bug 1323095

Summary:	Resource group with a nested wait condition handle fails on create
Product:	Red Hat OpenStack	Reporter:	VIKRANT <vaggarwa>
Component:	openstack-heat	Assignee:	Zane Bitter <zbitter>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.0 (Juno)	CC:	dmaley, mburns, rhel-osp-director-maint, sbaker, shardy, srevivo, zbitter
Target Milestone:	async	Keywords:	ZStream
Target Release:	6.0 (Juno)
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-heat-2014.2.4-1.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-23 18:37:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1323338
Bug Blocks:

Description VIKRANT 2016-04-01 09:26:14 UTC

Description of problem:
Resource group with a nested wait condition handle fails on create

Version-Release number of selected component (if applicable):
RHEL OSP 6
rpm -qa | grep -i heat
python-heatclient-0.2.12-1.el7ost.noarch
openstack-heat-engine-2014.2.3-11.el7ost.noarch
openstack-heat-common-2014.2.3-11.el7ost.noarch
openstack-heat-api-2014.2.3-11.el7ost.noarch


How reproducible:
Everytime.

Steps to Reproduce:
1. Steps are given in upstream Bug # Check C#1.
https://bugs.launchpad.net/heat/+bug/1402894
2.
3.

Actual results:
Stack is getting failed.

Expected results:
Stack should get crated successfully.

Additional info:

upstream bug opened this issue : 

https://bugs.launchpad.net/heat/+bug/1402894

Strangely, i can see the same behaviour in kilo as well with old and new heat_template_version "2014-10-16" both.

Comment 2 Zane Bitter 2016-04-02 00:12:43 UTC

I think we'll try to pick this up in a rebase, since it is already in an upstream stable release.

Comment 14 errata-xmlrpc 2016-06-23 18:37: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://access.redhat.com/errata/RHBA-2016:1314