Bug 1106858

Summary:	rhos5 is unable to create instances
Product:	Red Hat OpenStack	Reporter:	Russell Bryant <rbryant>
Component:	openstack-heat	Assignee:	Jeff Peeler <jpeeler>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.0 (RHEL 7)	CC:	apevec, augol, ddomingo, esammons, fpercoco, iboverma, jpeeler, jross, kgiusti, lhh, lzhaldyb, pematous, sbaker, sdake, shardy, tross, tshefi, yeylon, zkraus
Target Milestone:	rc	Keywords:	TestBlocker
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-heat-2014.1-1.5.el7ost	Doc Type:	Bug Fix
Doc Text:	In previous releases, a bug in the way QPID communicated with the broker made it possible for a required routing key to be left out of the address for a direct producer. Whenever this occurred, instances could not be launched. This release addresses the bug, thereby ensuring that routing keys are always specified in the address for a direct producer.	Story Points:	---
Clone Of:	1103800	Environment:
Last Closed:	2014-07-08 15:33:03 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:
Embargoed:
Bug Depends On:	1103800, 1106863, 1106893
Bug Blocks:	1106851, 1106854

Comment 1 Russell Bryant 2014-06-09 18:32:19 UTC

The oslo-incubator patch needed here is: https://review.openstack.org/#/c/98848/

Comment 2 Russell Bryant 2014-06-09 20:59:30 UTC

Heat master: https://review.openstack.org/98894
Heat stable/icehouse: https://review.openstack.org/98895

Comment 3 Petr Matousek 2014-06-17 06:44:39 UTC

Note: this issue is fixed, please see bug 1106854 comment 12 for details.

Comment 4 Amit Ugol 2014-06-17 06:47:49 UTC

I am waiting for the next puddle so I can see that this fix was introduced there.

Comment 6 Amit Ugol 2014-06-25 09:37:54 UTC

This is intruduced in the latest puddle.

Comment 10 errata-xmlrpc 2014-07-08 15:33:03 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.

http://rhn.redhat.com/errata/RHEA-2014-0849.html