This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 880360

Summary: HA replication of propagated bindings can lead to incorrect configuration
Product: Red Hat Enterprise MRG Reporter: Justin Ross <jross>
Component: qpid-cppAssignee: Chuck Rolke <crolke>
Status: CLOSED ERRATA QA Contact: Irina Boverman <iboverma>
Severity: unspecified Docs Contact:
Priority: high    
Version: DevelopmentCC: freznice, iboverma, jdillama, jross, lzhaldyb, mtoth
Target Milestone: 3.0Keywords: OtherQA, Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: 2.3 Doc Type: Bug Fix
Doc Text:
It was discovered that when using dynamic federation between two independent HA broker clusters, it was possible under certain failover scenarios for the propagated bindings on the source broker to become out-of-sync with the actual state of bindings on the destination broker. With the loss of the client subscription to the auto-delete queue, the binding was removed. If the binding was removed prior to the re-establishment of the federated link to the source broker, the unbind command did not propagate. Because the backup source broker had previously replicated the propagated binding, the binding incorrectly remained on the source broker. The fix prevents propagated bindings replicating from primary to back-up brokers. Transient bindings are recreated when the route is re-established and configurations remain synchronized.
Story Points: ---
Clone Of: 876688 Environment:
Last Closed: 2014-09-24 11:05:41 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 876688    
Bug Blocks: 698367    

Comment 8 errata-xmlrpc 2014-09-24 11:05:41 EDT
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.