Bug 1311180 - rabbitmq-cluster agent needs to forget stopped cluster nodes
Summary: rabbitmq-cluster agent needs to forget stopped cluster nodes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On: 1247303
Blocks: 1350073 1357991 1387985
TreeView+ depends on / blocked
 
Reported: 2016-02-23 14:48 UTC by Jan Kurik
Modified: 2019-10-10 11:18 UTC (History)
16 users (show)

Fixed In Version: resource-agents-3.9.5-54.el7_2.7
Doc Type: Bug Fix
Doc Text:
Cause: rabbitmq doesnt forget members quick enough Consequence: After fencing, a rabbitmq-cluster resource instance may not be able to rejoin the rabbitmq cluster. Fix: Use "rabbitmqctl forget_cluster_node <node>" when a node is fenced Result: Node is removed from cluster and can join again
Clone Of: 1247303
Environment:
Last Closed: 2016-03-31 22:08:41 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0556 0 normal SHIPPED_LIVE resource-agents bug fix update 2016-04-01 01:53:30 UTC

Description Jan Kurik 2016-02-23 14:48:54 UTC
This bug has been copied from bug #1247303 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 9 Leonid Natapov 2016-03-20 13:09:37 UTC
verified resource-agents-3.9.5-54.el7

[root@overcloud-controller-0 heat-admin]# pcs resource show rabbitmq
 Resource: rabbitmq (class=ocf provider=heartbeat type=rabbitmq-cluster)
  Attributes: set_policy="ha-all ^(?!amq\.).* {"ha-mode":"all"}" 
  Meta Attrs: notify=true 
  Operations: start interval=0s timeout=100 (rabbitmq-start-interval-0s)
              stop interval=0s timeout=90 (rabbitmq-stop-interval-0s)
              monitor interval=10 timeout=40 (rabbitmq-monitor-interval-10)

Comment 11 errata-xmlrpc 2016-03-31 22:08:41 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-2016-0556.html

Comment 12 Peter Lemenkov 2016-06-24 13:33:27 UTC
If someone still sees this issue, then please test this package:

resource-agents-3.9.5-76.el7


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