Bug 1038641 - [oslo] With QPID, RPC calls to a topic are always fanned-out to all subscribers.
Summary: [oslo] With QPID, RPC calls to a topic are always fanned-out to all subscribers.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 4.0
Assignee: Vladan Popovic
QA Contact: Jakub Ruzicka
URL:
Whiteboard:
: 1045066 (view as bug list)
Depends On:
Blocks: 1045066
TreeView+ depends on / blocked
 
Reported: 2013-12-05 14:39 UTC by Ken Giusti
Modified: 2019-09-09 13:28 UTC (History)
11 users (show)

Fixed In Version: openstack-nova-2013.2-9.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.
Clone Of:
: 1038714 1038716 1038717 1038718 1045066 (view as bug list)
Environment:
Last Closed: 2013-12-20 00:32:53 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1257293 0 None None None Never
Red Hat Bugzilla 1038714 0 high CLOSED [oslo] With QPID, RPC calls to a topic are always fanned-out to all subscribers. 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1038716 0 high CLOSED [oslo] With QPID, RPC calls to a topic are always fanned-out to all subscribers. 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1038717 0 high CLOSED [oslo] With QPID, RPC calls to a topic are always fanned-out to all subscribers. 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1038718 0 high CLOSED [oslo] With QPID, RPC calls to a topic are always fanned-out to all subscribers. 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2013:1859 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Internal Links: 1038714 1038716 1038717 1038718

Description Ken Giusti 2013-12-05 14:39:42 UTC 
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:
Comment 3 Perry Myers 2013-12-05 16:30:41 UTC 
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 4 Russell Bryant 2013-12-05 17:02:06 UTC 
(In reply to Perry Myers from comment #3)
> 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?)

It's an important fix, for sure.  Note that it doesn't affect the default configuration.  This only affects if the v2 topology is enabled.  So, it doesn't necessarily have to be a blocker, but we'd need a release note saying not to use the v2 topology at all yet.  We should get this in if we can and avoid that.
Comment 13 errata-xmlrpc 2013-12-20 00:32:53 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
Comment 15 Vladan Popovic 2014-01-14 18:11:25 UTC 
*** Bug 1045066 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.