Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
The ability with pcs to update the node names/address associated with rings in the /etc/corosync/corosync.conf file In addition, update the pacemaker cib.xml file with any changes.
For example, if the end user needed to change their hostname from and update their /etc/hosts entry:
node42.example2.com
To
node43.example7.com
Currently this is manual process that requires editing multiple files or commands (like changing pcmk_host_map) which has high probability of introducing typos and errors.
For example a pcs option similar to the following (this assumes the customer has already configured the new hostname and updated /etc/hosts) before running the command:
# pcs node rename <old name> <new name> ring0_addr=<new name> ring1_addr=<another name>
Version-Release number of selected component (if applicable):
pcs-0.9.162-5.el7_5.1.x86_64
How reproducible:
Does not apply
Steps to Reproduce:
Does not apply
Actual results:
Currently this is manual process that requires editing multiple files which has high probability of introducing typos and errors
Expected results:
The ability to change a cluster nodes name with a pcs command.
Additional info:
A related issue to this is that there is no way to modify, add, remove rings in an existing cluster without manually editing of files.
- How do i add or remove support for RRP on a existing pacemaker cluster?
https://access.redhat.com/solutions/3354671
There is an existing bugzilla on modifying attributes for corosync already:
- Bug 1173346 – Allow to modify arbitrary corosync.conf value
https://bugzilla.redhat.com/show_bug.cgi?id=1173346
- Editing the corosync.conf file in Red Hat Enterprise Linux 7
https://access.redhat.com/articles/3185291
I realize a change like this would require a restart of the cluster node as I do not see a way around a restart of pacemaker for this type of rfe after node name changed.
Comment 11RHEL Program Management
2023-09-22 18:16:51 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 12RHEL Program Management
2023-09-22 18:19:11 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: The ability with pcs to update the node names/address associated with rings in the /etc/corosync/corosync.conf file In addition, update the pacemaker cib.xml file with any changes. For example, if the end user needed to change their hostname from and update their /etc/hosts entry: node42.example2.com To node43.example7.com Currently this is manual process that requires editing multiple files or commands (like changing pcmk_host_map) which has high probability of introducing typos and errors. For example a pcs option similar to the following (this assumes the customer has already configured the new hostname and updated /etc/hosts) before running the command: # pcs node rename <old name> <new name> ring0_addr=<new name> ring1_addr=<another name> Version-Release number of selected component (if applicable): pcs-0.9.162-5.el7_5.1.x86_64 How reproducible: Does not apply Steps to Reproduce: Does not apply Actual results: Currently this is manual process that requires editing multiple files which has high probability of introducing typos and errors Expected results: The ability to change a cluster nodes name with a pcs command. Additional info: A related issue to this is that there is no way to modify, add, remove rings in an existing cluster without manually editing of files. - How do i add or remove support for RRP on a existing pacemaker cluster? https://access.redhat.com/solutions/3354671 There is an existing bugzilla on modifying attributes for corosync already: - Bug 1173346 – Allow to modify arbitrary corosync.conf value https://bugzilla.redhat.com/show_bug.cgi?id=1173346 - Editing the corosync.conf file in Red Hat Enterprise Linux 7 https://access.redhat.com/articles/3185291 I realize a change like this would require a restart of the cluster node as I do not see a way around a restart of pacemaker for this type of rfe after node name changed.