Bug 1402511 - RabbitMQ server crash with a core dump after fencing of one or more controllers
Summary: RabbitMQ server crash with a core dump after fencing of one or more controllers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Peter Lemenkov
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1397393
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 17:27 UTC by Marcel Kolaja
Modified: 2017-03-02 17:12 UTC (History)
16 users (show)

Fixed In Version: resource-agents-3.9.5-82.el7_3.5
Doc Type: Bug Fix
Doc Text:
Previously, when fencing controllers on Red Hat OpenStack Platform, the RabbitMQ resource terminated unexpectedly with a core dump. This update fixes how the RabbitMQ resource agent handles fencing, and thus avoids the described crash.
Clone Of: 1397393
Environment:
Last Closed: 2017-03-02 17:12:22 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ClusterLabs resource-agents pull 897 0 None None None 2016-12-07 17:27:18 UTC
Github rabbitmq rabbitmq-server pull 946 0 None None None 2016-12-07 17:27:18 UTC
Launchpad 1620649 0 None None None 2016-12-07 17:27:18 UTC
Red Hat Product Errata RHBA-2017:0382 0 normal SHIPPED_LIVE resource-agents bug fix update 2017-03-02 22:05:45 UTC

Description Marcel Kolaja 2016-12-07 17:27:07 UTC
This bug has been copied from bug #1397393 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 10 errata-xmlrpc 2017-03-02 17:12:22 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-2017-0382.html


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