RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1247303 - 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:
: 1299923 (view as bug list)
Depends On: 1311025
Blocks: 1311180
TreeView+ depends on / blocked
 
Reported: 2015-07-27 18:09 UTC by David Vossel
Modified: 2021-06-10 10:56 UTC (History)
17 users (show)

Fixed In Version: resource-agents-3.9.5-60.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1311180 (view as bug list)
Environment:
Last Closed: 2016-11-03 23:57:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2174 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2016-11-03 13:16:36 UTC

Description David Vossel 2015-07-27 18:09:58 UTC 
Description of problem:

After fencing, a rabbitmq-cluster resource instance may not be able to rejoin the rabbitmq cluster.

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


How reproducible:
We have seen this in customer deployments. This is not something that has a clear set of steps to reproduce.

Steps to Reproduce:
1. fence a osp cluster node.

Actual results:
rabbitmq-cluster instance on fenced node can not join rabbitmq cluster once node comes back online.

Expected results:
rabbitmq-cluster instance on fenced node should be able to start successfully after the node comes back online.
Comment 1 David Vossel 2015-07-27 18:11:26 UTC 
upstream patch.

https://github.com/davidvossel/resource-agents/commit/f82b1f794df8af69371572dcd83e76792953ada9
Comment 5 Fabio Massimo Di Nitto 2015-09-01 03:20:37 UTC 
John,

did you have a chance to test this patch again? is it still required?
Comment 6 John Eckersberg 2015-09-01 12:47:40 UTC 
I still need to go back and test this.  The libvirt fence agent wasn't working for me, but David realized it was because the hostname and the libvirt domain name didn't match.  So I need to try that and see if I can get it to fence properly.

Leaving NEEDINFO for now to remind me to actually try it :)
Comment 7 Fabio Massimo Di Nitto 2015-09-03 03:35:31 UTC 
(In reply to John Eckersberg from comment #6)
> I still need to go back and test this.  The libvirt fence agent wasn't
> working for me, but David realized it was because the hostname and the
> libvirt domain name didn't match.  So I need to try that and see if I can
> get it to fence properly.
> 
> Leaving NEEDINFO for now to remind me to actually try it :)

That´s fine, but we don´t have heaps of time to get this into 7.2. If you need help to configure fencing or other bits, please just contact me or #cluster.
Comment 9 Oyvind Albrigtsen 2015-11-20 12:37:36 UTC 
Works as expected.

Tested with:
# service corosync stop &
# killall -9 corosync

on the node that should be fenced.

First notify:
rabbitmq-cluster(rmq)[15072]:   2015/11/20_13:30:10 NOTICE: Forgetting stopped node rabbit@rhel7-1
rabbitmq-cluster(rmq)[15072]:   2015/11/20_13:30:11 WARNING: Unable to forget offline node rabbit@rhel7-1.

Second notify:
rabbitmq-cluster(rmq)[15284]:   2015/11/20_13:30:26 NOTICE: Forgetting stopped node rabbit@rhel7-1
Comment 13 Fabio Massimo Di Nitto 2016-02-23 14:08:09 UTC 
*** Bug 1299923 has been marked as a duplicate of this bug. ***
Comment 21 Leonid Natapov 2016-03-09 09:30:57 UTC 
resource-agents-3.9.5-67.el7

Looks good:

After fencing controller-0 I see the following on controller-1 and controller-2:

overcloud-controller-1 
-------------------------
rabbitmq-cluster(rabbitmq)[32276]:	2016/03/09_09:19:35 NOTICE: Forgetting stopped node rabbit@overcloud-controller-0
rabbitmq-cluster(rabbitmq)[32276]:	2016/03/09_09:19:35 WARNING: Unable to forget offline node rabbit@overcloud-controller-0.

overcloud-controller-2
-------------------------
rabbitmq-cluster(rabbitmq)[16925]:	2016/03/09_09:19:35 NOTICE: Forgetting stopped node rabbit@overcloud-controller-0


Works as expected.
Comment 22 Peter Lemenkov 2016-06-24 13:33:09 UTC 
(In reply to Leonid Natapov from comment #21)
> resource-agents-3.9.5-67.el7
> 
> Looks good:
> 
> After fencing controller-0 I see the following on controller-1 and
> controller-2:
> 
> overcloud-controller-1 
> -------------------------
> rabbitmq-cluster(rabbitmq)[32276]:	2016/03/09_09:19:35 NOTICE: Forgetting
> stopped node rabbit@overcloud-controller-0
> rabbitmq-cluster(rabbitmq)[32276]:	2016/03/09_09:19:35 WARNING: Unable to
> forget offline node rabbit@overcloud-controller-0.
> 
> overcloud-controller-2
> -------------------------
> rabbitmq-cluster(rabbitmq)[16925]:	2016/03/09_09:19:35 NOTICE: Forgetting
> stopped node rabbit@overcloud-controller-0
> 
> 
> Works as expected.

If someone still sees this issue, then please test this package:

resource-agents-3.9.5-76.el7
Comment 24 errata-xmlrpc 2016-11-03 23:57:47 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-2174.html
Note You need to log in before you can comment on or make changes to this bug.