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.

Recent RabbitMQ versions return "69" when a node isn't running. Previous
versions return "2" in this case. This change was introduced in commit - https://github.com/rabbitmq/rabbitmq-server/commit/798454.

Fix was introduced in the following PR - https://github.com/ClusterLabs/resource-agents/pull/818.

See bug 1338657 comment 8 for further details.

How to test:

* Deploy a cluster of RabbitMQ using an old version (anything from 3.3.5 line - RHOS6, RHOS7, RHOS8).
* Start RabbitMQ cluster.
* Everything starts normally.

* Deploy a cluster of RabbitMQ using a new version (latest 3.6.2 build or higher - available in RHOS9 and later) and using the same resource-agents version.
* Start RabbitMQ cluster.
* Everything starts normally.

New build with additional return codes from: https://github.com/ClusterLabs/resource-agents/pull/833

Yes, I can confirm that this build (resource-agents-3.9.5-77.el7) contains the necessary patch.

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