Bug 1303747 - Blocked channels and queues using HA
Summary: Blocked channels and queues using HA
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: 6.0 (Juno)
Assignee: Peter Lemenkov
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On: 1303745
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-01 20:07 UTC by John Eckersberg
Modified: 2016-04-26 13:57 UTC (History)
9 users (show)

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.
Clone Of: 1303745
Environment:
Last Closed: 2016-02-29 05:10:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:0308 0 normal SHIPPED_LIVE Moderate: rabbitmq-server security and bugfix update 2016-02-29 10:09:51 UTC

Description John Eckersberg 2016-02-01 20:07:40 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:34:54 UTC
Build a rabbitmq-server-3.3.5-8.6.el7ost for rhos-6.0-rhel-7.

Comment 7 errata-xmlrpc 2016-02-29 05:10:51 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-0308.html


Note You need to log in before you can comment on or make changes to this bug.