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.

Description of problem: An attempted connection to a Pacemaker Remote node that already is integrated into a cluster will disconnect the node from the cluster, and the cluster host's crmd may print garbled log messages and/or crash.


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


How reproducible: easily/consistently


Steps to Reproduce:
1. Configure a Pacemaker cluster including a Pacemaker Remote node.
2. Start the cluster and wait for the remote node to integrate.
3. From any machine with access to the Pacemaker Remote port, run "nc -t <nodename> 3121".

Actual results: Remote node will be disconnected from the cluster, its monitor operation will fail, and the cluster node hosting its connection may have crmd crash or print log messages with random characters.


Expected results: The attempted connection fails, and the cluster is unaffected.

This was fixed upstream as of 5ec24a2, and the necessary patches were included in the latest build for #1252206. This BZ was added for tracking and QA purposes.

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-0856.html