Bug 1082670

Summary:	connection to multiple qpidd instances is broken
Product:	Red Hat OpenStack	Reporter:	Ihar Hrachyshka <ihrachys>
Component:	openstack-nova	Assignee:	Russell Bryant <rbryant>
Status:	CLOSED ERRATA	QA Contact:	Sean Toner <stoner>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.0	CC:	breeler, chrisw, fdinitto, fpercoco, gsim, kgiusti, lpeer, markmc, ndipanov, sgordon, stoner, tdunnon, vpopovic, yeylon
Target Milestone:	async	Keywords:	OtherQA, ZStream
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-2013.2.3-9.el6ost	Doc Type:	Bug Fix
Doc Text:	Previously, when a qpid connection failed, Compute services would always attempt to re-connect to the broker using the list of broker addresses, starting at the beginning. As a result, if the first address is the one that went down, Compute would immediately always try to reconnect to that one first and get nowhere. This has been fixed by ensuring that Compute always reconnects to the next broker in the list from the last one that was attempted or connected to. Now, if multiple broker addresses are configured for qpidd, Compute will always try a different one from the one that just failed.	Story Points:	---
Clone Of:	1082661	Environment:
Last Closed:	2014-08-21 00:39:48 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:	1036523, 1082672
Bug Blocks:	1080561, 1082661, 1082664, 1082665, 1082666, 1082668, 1082669, 1123376

Comment 4 Ihar Hrachyshka 2014-08-12 12:20:08 UTC

@Sean, you can separate multiple qpid hosts in neutron.conf with a comma:

qpid_hosts = host1:5672,host2:5672,host3:5672

Of course, all Qpid hosts should be in single cluster.

Comment 6 errata-xmlrpc 2014-08-21 00:39:48 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/RHSA-2014-1084.html