Bug 1038718

Summary:	[oslo] With QPID, RPC calls to a topic are always fanned-out to all subscribers.
Product:	Red Hat OpenStack	Reporter:	Perry Myers <pmyers>
Component:	openstack-cinder	Assignee:	Flavio Percoco <fpercoco>
Status:	CLOSED ERRATA	QA Contact:	Haim <hateya>
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	breeler, dallan, ddomingo, dron, eharney, fpercoco, hateya, kgiusti, ndipanov, yeylon
Target Milestone:	rc	Keywords:	OtherQA
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-cinder-2013.2-7.el6ost	Doc Type:	Bug Fix
Doc Text:	When the QPID broker is restarted, RPC servers attempt to re-connect. However, a bug in the QPID topic consumer re-connection logic (under the v2 topology) caused qpidd to use a malformed subscriber address after restarting. As a result, RPC requests sent to a topic with multiple servers ended up being incorrectly multicast to all servers. This release removes the special-case reconnect logic that handles UUID addresses, which in turn avoids the incorrect establishment of multiple subscription to the same fanout address. The QPID broker will simply generate unique queue names automatically when clients reconnect.	Story Points:	---
Clone Of:	1038641	Environment:
Last Closed:	2013-12-20 00:43: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:

Description Perry Myers 2013-12-05 16:39:25 UTC

+++ This bug was initially created as a clone of Bug #1038641 +++

Description of problem:


  See upstream bug:

  https://bugs.launchpad.net/oslo/+bug/1257293

  Note well: this bug _only_ affects those QPID configurations that have applied the fix of the following bug:

   https://bugs.launchpad.net/oslo/+bug/1178375


  _AND_ are have configured "qpid_topology_version=2"



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from RHEL Product and Program Management on 2013-12-05 09:44:55 EST ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Dave Allan on 2013-12-05 10:11:18 EST ---

Checking into risk of fix; may want to take for 4.0GA

--- Additional comment from Perry Myers on 2013-12-05 11:30:41 EST ---

This seems important enough to be an RC blocker for 4.0.  But doesn't this bug need to be cloned to Nova, Ceilometer, Neutron, etc (every component that copies and pastes the code from Oslo for RPC?)

Comment 5 errata-xmlrpc 2013-12-20 00:43: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-2013-1859.html