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 and update their /etc/hosts entry from "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:

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.

Acceptance criteria

• Commands available for updating node names in corosync and pacemaker configuration.
  • For more details see upstream development tickets: RHELHA-687, RHELHA-688
• Draft of an updated Solution article (that should be published once errata fixing this ticket is released) available describing a procedure for renaming cluster nodes with use of the newly introduced commands.
  • The updated procedure for renaming cluster nodes needs to be able to rename multiple cluster nodes (including all nodes) and optionally allow to also change node addresses.
  • For more details see RHELHA-689