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.

Currently pcs/pcsd talks to other cluster nodes using ring0 addresses only. When RRP is configured in a cluster and a node is not available using its ring0 address, a ring1 address should be used to reach the node.

Issues to think about:
* authorization to different addresses of a node
* "pcs status pcsd" should probably display status for all nodes' addresses

This has been already requested on a mailing list:
http://clusterlabs.org/pipermail/users/2015-November/001860.html

This requires a major overhaul of code related to node to node communication and authentication. It has partially been done in pcs-0.10 branch, so it is possible to follow up with this functionality there (bz1649255). The pcs-0.10 branch cannot be included in RHEL7 as it does not support Corosync 2.x and Pacemaker 1.x. Backporting to pcs-0.9 will not happen as there are fundamental changes which are not compatible with pcs-0.9.