Bug 886656

Summary: HA backup broker does not properly increment the alternate exchange user count
Product: Red Hat Enterprise MRG Reporter: Jason Dillaman <jdillama>
Component: qpid-cppAssignee: Alan Conway <aconway>
Status: CLOSED CURRENTRELEASE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: unspecified Docs Contact:
Priority: medium    
Version: DevelopmentCC: esammons, iboverma, jross, mcressma
Target Milestone: 2.3Keywords: OtherQA
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: qpid-cpp-0.18-14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-19 12:40:08 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: 886262    
Bug Blocks: 698367    
Description Flags
Patch to add a unit test reproducer none

Description Jason Dillaman 2012-12-12 14:54:28 EST
Description of problem:
When an exchange or queue that utilizes an alternate exchange is replicated to a backup broker, the backup broker does not increment the user count on the alternate exchange.  This will incorrectly allow an alternate exchange to be deleted when it is still in use and will incorrectly prevent a exchange from being deleted when it is no longer an alternate exchange.

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

How reproducible:

Steps to Reproduce:
1. Start primary and backup HA brokers
2. Create an exchange to use as the alternate
3. Create a queue or exchange w/ the alternate set to the previously create exchange
4. Fail the primary and promote the backup
5. Delete the alternate exchange
Actual results:
The alternate exchange is deleted while still in use

Expected results:
The client should receive a not-allowed exception

Additional info:
Comment 1 Jason Dillaman 2012-12-12 14:55:07 EST
Created attachment 662585 [details]
Patch to add a unit test reproducer
Comment 3 Alan Conway 2012-12-20 15:08:32 EST
Seeing some problems that may be due to this fix in testing. Marking this bug ASSIGNED again.