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.

To elaborate a bit more:

* "remote node" is still the proper term and capitalization of a node integrated into the cluster via ocf:pacemaker:remote

* "Pacemaker Remote" is the general technology encompassing all the parts (pacemaker_remote, ocf:pacemaker:remote, remote-node, etc.).

* "Pacemaker Remote node" is my own term and not official, to refer to "guest node or remote node". Substituting something else in the name of clarity is fine.

I went through the product doc and there were just a couple of references to a "Pacemaker remote" note (as opposed to a "remote node"), so I changed that to the capitalization noted here of Pacemaker Remote node, although I'm not sure that this distinction will read to the user.  I'm also not not sure that every instance of "remote node" does not refer to "remote or guest node", but this documentation has been reviewed a few times so anything confusing should have been flagged at that point.  For now I just went with the "Pacemaker Remote" in the few places where we had previously said "Pacemaker remote" because that's consistent with the screen display.