Bug 1038711 - [oslo] On restart of QPID or reconnect to QPID, fanout RPC no longer works
Summary: [oslo] On restart of QPID or reconnect to QPID, fanout RPC no longer works
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 4.0
Assignee: Terry Wilson
QA Contact: Ihar Hrachyshka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 16:34 UTC by Perry Myers
Modified: 2019-09-09 13:58 UTC (History)
11 users (show)

Fixed In Version: openstack-neutron-2013.2-14.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. This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for individual services (e.g. Neutron). 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: 1038638
Environment:
Last Closed: 2013-12-20 00:41:23 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 1251757 0 None None None Never
Red Hat Bugzilla 1038638 0 high CLOSED [oslo] On restart of QPID or reconnect to QPID, fanout RPC no longer works 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: 1038638

Description Perry Myers 2013-12-05 16:34:40 UTC 
+++ This bug was initially created as a clone of Bug #1038638 +++

Description of problem:

   See upstream bug report:

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


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:45:05 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:12:09 EST ---

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

--- Additional comment from Perry Myers on 2013-12-05 11:29:29 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 4 Ihar Hrachyshka 2013-12-17 17:00:07 UTC 
Verified the bug against qpid-cpp-server-0.18-14.el6. After 'service qpidd restart', the following subsriptions are renewed by testing server (snippet from qpidd trace=yes feature):

Dec 17 17:55:27 rhel65 qpidd[8242]: 2013-12-17 17:55:27 [Broker] info Queue "my-topic": Policy created: type=reject; maxCount=0; maxSize=104857600
Dec 17 17:55:27 rhel65 qpidd[8242]: 2013-12-17 17:55:27 [Broker] info Queue "5345635b-19c6-4186-92e2-bf2d997b7264:0.1": Policy created: type=reject; maxCount=0; maxSize=104857600
Dec 17 17:55:27 rhel65 qpidd[8242]: 2013-12-17 17:55:27 [Broker] info Queue "my-topic.server-02": Policy created: type=reject; maxCount=0; maxSize=104857600

I guess this means the bug is fixed. But I'm not sure whether this is enough to verify this specific bug which is opened for openstack-neutron package, not just oslo.

Ofer, again, can you elaborate on whether the check I've done is enough to verify the bug?
Comment 5 Ihar Hrachyshka 2013-12-17 17:32:42 UTC 
As per Livnat's suggestion, marking the bug as verified.
Comment 7 Ihar Hrachyshka 2013-12-18 08:23:24 UTC 
We can use the following testing utilities to create fanout exchanges: https://github.com/kgiusti/oslo-messaging-clients
Comment 9 errata-xmlrpc 2013-12-20 00:41:23 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
Note You need to log in before you can comment on or make changes to this bug.