Bug 1620043

Cluster name is defined in corosync.conf so it makes sense to me it is not possible to change it in pacemaker. Details of why pacemaker actually allows the cluster-name CIB property to be changed and what impact that may have would have to be provided by pacemaker team.

Is this an RFE to add possibility to rename clusters?

As a user, I would expect this to be possible, since you actually do specify cluster name to pcs when creating the cluster (with "pcs cluster setup") and seeing the cluster-name property in the output of "pcs property" only reinforces this expectation.

Given your comment, I would consider this an UX RFE with four possible solutions (in order of preference):
  1) allowing the cluster name to be properly changed with "pcs property set cluster-name=..." (and also implementing the solution below for other properties)
  2) somehow marking immutable properties in "pcs property" output and showing a better error message when a modification is attempted (this would also apply to other properties, eg. dc-version)
  3) printing a hint to make the change in corosync.conf when user attempts to set it via "pcs property set cluster-name=..." (retaining the error message and exit code > 0)
  4) completely removing cluster-name from "pcs property" output

What do you think?

Note that in otherwise discouraged scenarios, the symmetric
cryptography key at corosync level might be derived from
the cluster name corosync/cman was aware of.  At least in RHEL 6
and with CMAN, changing cluster name deliberately might break
the running cluster, so better to recheck the consequences of
changing that value first.

Related: [bug 1173346]

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Upstream commit: https://github.com/ClusterLabs/pcs/commit/f51fdd340147b72c6099864f649cfbbe5f4051d4
Updated commands:
  * pcs property set
  * pcs property unset

It is not possible to modify specific pacemaker cluster properties: "cluster-infrastructure", "cluster-name", "dc-version", "have-watchdog","last-lrm-refresh".

Test:

[root@r9-node-01 ~]# pcs property set cluster-name=NewName
Error: invalid cluster property option 'cluster-name', allowed options are: 'batch-limit', 'cluster-delay', 'cluster-ipc-limit', 'cluster-recheck-interval', 'concurrent-fencing', 'dc-deadtime', 'election-timeout', 'enable-acl', 'enable-startup-probes', 'fence-reaction', 'join-finalization-timeout', 'join-integration-timeout', 'load-threshold', 'maintenance-mode', 'migration-limit', 'no-quorum-policy', 'node-action-limit', 'node-health-base', 'node-health-green', 'node-health-red', 'node-health-strategy', 'node-health-yellow', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', 'remove-after-stop', 'shutdown-escalation', 'shutdown-lock', 'shutdown-lock-limit', 'start-failure-is-fatal', 'startup-fencing', 'stonith-action', 'stonith-enabled', 'stonith-max-attempts', 'stonith-timeout', 'stonith-watchdog-timeout', 'stop-all-resources', 'stop-orphan-actions', 'stop-orphan-resources', 'symmetric-cluster', 'transition-delay'
Error: Errors have occurred, therefore pcs is unable to continue

[root@r9-node-01 ~]# pcs property set cluster-name=NewName --force
Error: invalid cluster property option 'cluster-name', allowed options are: 'batch-limit', 'cluster-delay', 'cluster-ipc-limit', 'cluster-recheck-interval', 'concurrent-fencing', 'dc-deadtime', 'election-timeout', 'enable-acl', 'enable-startup-probes', 'fence-reaction', 'join-finalization-timeout', 'join-integration-timeout', 'load-threshold', 'maintenance-mode', 'migration-limit', 'no-quorum-policy', 'node-action-limit', 'node-health-base', 'node-health-green', 'node-health-red', 'node-health-strategy', 'node-health-yellow', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', 'remove-after-stop', 'shutdown-escalation', 'shutdown-lock', 'shutdown-lock-limit', 'start-failure-is-fatal', 'startup-fencing', 'stonith-action', 'stonith-enabled', 'stonith-max-attempts', 'stonith-timeout', 'stonith-watchdog-timeout', 'stop-all-resources', 'stop-orphan-actions', 'stop-orphan-resources', 'symmetric-cluster', 'transition-delay'
Error: Errors have occurred, therefore pcs is unable to continue

[root@r9-node-01 ~]# pcs property config cluster-name
Cluster Properties:
 cluster-name: HACluster

[root@r9-node-01 ~]# pcs property unset cluster-name
Error: invalid cluster property option 'cluster-name', allowed options are: 'batch-limit', 'cluster-delay', 'cluster-ipc-limit', 'cluster-recheck-interval', 'concurrent-fencing', 'dc-deadtime', 'election-timeout', 'enable-acl', 'enable-startup-probes', 'fence-reaction', 'join-finalization-timeout', 'join-integration-timeout', 'load-threshold', 'maintenance-mode', 'migration-limit', 'no-quorum-policy', 'node-action-limit', 'node-health-base', 'node-health-green', 'node-health-red', 'node-health-strategy', 'node-health-yellow', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', 'remove-after-stop', 'shutdown-escalation', 'shutdown-lock', 'shutdown-lock-limit', 'start-failure-is-fatal', 'startup-fencing', 'stonith-action', 'stonith-enabled', 'stonith-max-attempts', 'stonith-timeout', 'stonith-watchdog-timeout', 'stop-all-resources', 'stop-orphan-actions', 'stop-orphan-resources', 'symmetric-cluster', 'transition-delay'
Error: Errors have occurred, therefore pcs is unable to continue

[root@r9-node-01 ~]# pcs property unset cluster-name --force
Error: invalid cluster property option 'cluster-name', allowed options are: 'batch-limit', 'cluster-delay', 'cluster-ipc-limit', 'cluster-recheck-interval', 'concurrent-fencing', 'dc-deadtime', 'election-timeout', 'enable-acl', 'enable-startup-probes', 'fence-reaction', 'join-finalization-timeout', 'join-integration-timeout', 'load-threshold', 'maintenance-mode', 'migration-limit', 'no-quorum-policy', 'node-action-limit', 'node-health-base', 'node-health-green', 'node-health-red', 'node-health-strategy', 'node-health-yellow', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', 'remove-after-stop', 'shutdown-escalation', 'shutdown-lock', 'shutdown-lock-limit', 'start-failure-is-fatal', 'startup-fencing', 'stonith-action', 'stonith-enabled', 'stonith-max-attempts', 'stonith-timeout', 'stonith-watchdog-timeout', 'stop-all-resources', 'stop-orphan-actions', 'stop-orphan-resources', 'symmetric-cluster', 'transition-delay'
Error: Errors have occurred, therefore pcs is unable to continue

DevTestResults:

[root@r09-02-a ~]# rpm -q pcs
pcs-0.11.4-1.el9.x86_64

[root@r09-02-a ~]# pcs property set cluster-name=NewName
Error: invalid cluster property option 'cluster-name', allowed options are: 'batch-limit', 'cluster-delay', 'cluster-ipc-limit', 'cluster-recheck-interval', 'concur
rent-fencing', 'dc-deadtime', 'election-timeout', 'enable-acl', 'enable-startup-probes', 'fence-reaction', 'join-finalization-timeout', 'join-integration-timeout',
'load-threshold', 'maintenance-mode', 'migration-limit', 'no-quorum-policy', 'node-action-limit', 'node-health-base', 'node-health-green', 'node-health-red', 'node-
health-strategy', 'node-health-yellow', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', 'remove-
after-stop', 'shutdown-escalation', 'shutdown-lock', 'shutdown-lock-limit', 'start-failure-is-fatal', 'startup-fencing', 'stonith-action', 'stonith-enabled', 'stoni
th-max-attempts', 'stonith-timeout', 'stonith-watchdog-timeout', 'stop-all-resources', 'stop-orphan-actions', 'stop-orphan-resources', 'symmetric-cluster', 'transit
ion-delay'
Error: Errors have occurred, therefore pcs is unable to continue

[root@r09-02-a ~]# pcs property set cluster-name=NewName --force
Error: invalid cluster property option 'cluster-name', allowed options are: 'batch-limit', 'cluster-delay', 'cluster-ipc-limit', 'cluster-recheck-interval', 'concur
rent-fencing', 'dc-deadtime', 'election-timeout', 'enable-acl', 'enable-startup-probes', 'fence-reaction', 'join-finalization-timeout', 'join-integration-timeout',
'load-threshold', 'maintenance-mode', 'migration-limit', 'no-quorum-policy', 'node-action-limit', 'node-health-base', 'node-health-green', 'node-health-red', 'node-
health-strategy', 'node-health-yellow', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', 'remove-
after-stop', 'shutdown-escalation', 'shutdown-lock', 'shutdown-lock-limit', 'start-failure-is-fatal', 'startup-fencing', 'stonith-action', 'stonith-enabled', 'stoni
th-max-attempts', 'stonith-timeout', 'stonith-watchdog-timeout', 'stop-all-resources', 'stop-orphan-actions', 'stop-orphan-resources', 'symmetric-cluster', 'transit
ion-delay'
Error: Errors have occurred, therefore pcs is unable to continue

[root@r09-02-a ~]# pcs property config cluster-name
Cluster Properties:
cluster-name: onenode

[root@r09-02-a ~]# pcs property unset cluster-name
Error: invalid cluster property option 'cluster-name', allowed options are: 'batch-limit', 'cluster-delay', 'cluster-ipc-limit', 'cluster-recheck-interval', 'concur
rent-fencing', 'dc-deadtime', 'election-timeout', 'enable-acl', 'enable-startup-probes', 'fence-reaction', 'join-finalization-timeout', 'join-integration-timeout',
'load-threshold', 'maintenance-mode', 'migration-limit', 'no-quorum-policy', 'node-action-limit', 'node-health-base', 'node-health-green', 'node-health-red', 'node-
health-strategy', 'node-health-yellow', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', 'remove-
after-stop', 'shutdown-escalation', 'shutdown-lock', 'shutdown-lock-limit', 'start-failure-is-fatal', 'startup-fencing', 'stonith-action', 'stonith-enabled', 'stoni
th-max-attempts', 'stonith-timeout', 'stonith-watchdog-timeout', 'stop-all-resources', 'stop-orphan-actions', 'stop-orphan-resources', 'symmetric-cluster', 'transit
ion-delay'
Error: Errors have occurred, therefore pcs is unable to continue

[root@r09-02-a ~]# pcs property unset cluster-name --force
Error: invalid cluster property option 'cluster-name', allowed options are: 'batch-limit', 'cluster-delay', 'cluster-ipc-limit', 'cluster-recheck-interval', 'concur
rent-fencing', 'dc-deadtime', 'election-timeout', 'enable-acl', 'enable-startup-probes', 'fence-reaction', 'join-finalization-timeout', 'join-integration-timeout',
'load-threshold', 'maintenance-mode', 'migration-limit', 'no-quorum-policy', 'node-action-limit', 'node-health-base', 'node-health-green', 'node-health-red', 'node-
health-strategy', 'node-health-yellow', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', 'remove-
after-stop', 'shutdown-escalation', 'shutdown-lock', 'shutdown-lock-limit', 'start-failure-is-fatal', 'startup-fencing', 'stonith-action', 'stonith-enabled', 'stoni
th-max-attempts', 'stonith-timeout', 'stonith-watchdog-timeout', 'stop-all-resources', 'stop-orphan-actions', 'stop-orphan-resources', 'symmetric-cluster', 'transit
ion-delay'
Error: Errors have occurred, therefore pcs is unable to continue

[root@r09-02-a ~]# pcs property config cluster-name
Cluster Properties:
cluster-name: onenode

The same test as in bz2112263 comment 6 was used on RHEL9 system with pcs-0.11.4-1.el9 to verify this bz.
Marking as VERIFIED.

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 (pcs bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:2151