Bug 1303748

Summary:	Blocked channels and queues using HA
Product:	Red Hat OpenStack	Reporter:	John Eckersberg <jeckersb>
Component:	rabbitmq-server	Assignee:	Peter Lemenkov <plemenko>
Status:	CLOSED ERRATA	QA Contact:	yeylon <yeylon>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	apevec, jeckersb, lhh, nlevinki, plemenko, scorcora, slong, srevivo, yeylon
Target Milestone:	async	Keywords:	ZStream
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rabbitmq-server-3.3.5-16.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, if the rabbit_mirror_queue_master did not return when using HA and 'auto_delete' queues, the RabbitMQ server blocked channels during termination. These channels would then have no associated connections and were displayed as 'unknown'. This issue has been resolved.	Story Points:	---
Clone Of:	1303745	Environment:
Last Closed:	2016-03-08 22:54:44 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:
Bug Depends On:	1303745
Bug Blocks:

Description John Eckersberg 2016-02-01 20:07:48 UTC

+++ This bug was initially created as a clone of Bug #1303745 +++

https://github.com/rabbitmq/rabbitmq-server/issues/581

Likely a problem in all OSP versions.  This would explain a lot of weird partition-related hangs and such.

Comment 1 Peter Lemenkov 2016-02-17 14:39:47 UTC

Build rabbitmq-server-3.3.5-8.5.el7ost for rhos-5.0-rhel-7.

Comment 6 nlevinki 2016-03-03 09:50:04 UTC

code is in
rabbitmq-server-3.3.5-18.el7ost.noarch
automation passed and this puddle fixed rabbit issues
https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/RHOS/view/RHOS5/job/rhos-jenkins-rhos-5.0-puddle-rhel-7.2-multi-node-packstack-neutron-ml2-gre-rabbitmq-tempest-git-all/12/

Comment 10 errata-xmlrpc 2016-03-08 22:54:44 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/RHSA-2016-0369.html