Bug 1188309

Summary: Declare DirectPublisher exchanges with passive=True
Product: Red Hat OpenStack Reporter: John Eckersberg <jeckersb>
Component: python-oslo-messagingAssignee: hguemar
Status: CLOSED ERRATA QA Contact: Udi Shkalim <ushkalim>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0 (Juno)CC: apevec, dmaley, fpercoco, goeran, hguemar, lhh, lnatapov, mlopes, oblaut, scohen, yeylon
Target Milestone: ---Keywords: TestOnly, Triaged, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-oslo-messaging-1.4.1-5.el7ost Doc Type: Bug Fix
Doc Text:
This update addresses potential race conditions involving the 'oslo' messaging backend used in RabbitMQ.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-24 14:48:33 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:
Attachments:
Description Flags
bug_1338732_script_resaults none

Description John Eckersberg 2015-02-02 15:08:59 UTC
From upstream change, https://review.openstack.org/#/c/109373/

"If rabbit dies, the consumer can be disconnected before the publisher
sends, and if the consumer hasn't declared the queue, the publisher's
will send a message to an exchange that's not bound to a queue, and
the message wll be lost.  Setting passive=True will cause the
publisher to fail and retry if the consumer hasn't declared the
receiving queue yet."

This change addresses this race condition.  It would be good to have it backported for RHOS-6.0.

Comment 7 Udi Shkalim 2015-08-18 14:49:28 UTC
Created attachment 1064343 [details]
bug_1338732_script_resaults

Comment 8 Udi Shkalim 2015-08-18 14:55:34 UTC
Verified.

Running the script from bug https://bugs.launchpad.net/oslo.messaging/+bug/1338732 before the fix got the same results (bug reproduced)

Running on the new version:
2014.2.3
python-oslo-messaging-1.4.1-5.el7ost.noarch

Script results changed (see attached).

Fix is also related to bug: https://bugzilla.redhat.com/show_bug.cgi?id=1188304
Which also verified.

Comment 10 errata-xmlrpc 2015-08-24 14:48:33 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.

https://rhn.redhat.com/errata/RHBA-2015-1659.html