Bug 2112263

Summary:	unable to change cluster name
Product:	Red Hat Enterprise Linux 8	Reporter:	Tomas Jelinek <tojeline>
Component:	pcs	Assignee:	Miroslav Lisik <mlisik>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:	Steven J. Levine <slevine>
Priority:	medium
Version:	8.0	CC:	cfeist, cluster-maint, cluster-qe, djansa, idevat, mlisik, mmazoure, mpospisi, omular, phagara, slevine, tojeline
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pcs-0.10.15-1.el8	Doc Type:	Bug Fix
Doc Text:	.`pcs` no longer allows you to modify cluster properties that should not be changed Previously, the `pcs` command line interface allowed you to modify cluster properties that should not be changed or for which change does not take effect. With this fix, `pcs` no longer allows you to modify these cluster properties: `cluster-infrastructure`, `cluster-name`, `dc-version`, `have-watchdog`, and `last-lrm-refresh`.	Story Points:	---
Clone Of:	1620043	Environment:
Last Closed:	2023-05-16 08:12:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas Jelinek 2022-07-29 08:03:46 UTC

+++ This bug was initially created as a clone of Bug #1620043 +++

Description of problem:
It is not possible to change the name of a cluster via "pcs property".


Version-Release number of selected component (if applicable):
> [root@virt-154 ~]# rpm -q pcs pacemaker
> pcs-0.9.165-4.el7.x86_64
> pacemaker-1.1.19-7.el7.x86_64


How reproducible:
always


Steps to Reproduce:

> [root@virt-154 ~]# pcs property 
> Cluster Properties:
>  cluster-infrastructure: corosync
>  cluster-name: STSRHTS13416
>  dc-version: 1.1.19-7.el7-c3c624ea3d
>  have-watchdog: false


Actual results:

> [root@virt-154 ~]# pcs property set cluster-name=new-name
> Error: unknown cluster property: 'cluster-name', (use --force to override)
> [root@virt-154 ~]# pcs property set --force cluster-name=new-name
> [root@virt-154 ~]# pcs property
> Cluster Properties:
>  cluster-infrastructure: corosync
>  cluster-name: new-name
>  dc-version: 1.1.19-7.el7-c3c624ea3d
>  have-watchdog: false
>  stonith-enabled: false
> [root@virt-154 ~]# pcs status
> Cluster name: STSRHTS13416
> ...

Cluster name does not change, even with --force. Additionally, "pcs property" reports wrong (new) value for cluster-name property after a forceful set, while the actual cluster name remains unchanged.


Expected results:
no error, cluster name changed

--- Additional comment from Tomas Jelinek on 2018-08-22 12:44:46 CEST ---

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?

--- Additional comment from Patrik Hagara on 2018-08-22 13:10:59 CEST ---

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?

--- Additional comment from Jan Pokorný [poki] on 2018-08-22 13:49:12 CEST ---

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]

Comment 1 Miroslav Lisik 2022-11-16 16:00:49 UTC

Upstream commit: https://github.com/ClusterLabs/pcs/commit/bfc1d290909cd61dddc8d602ca92869c95697616
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@r8-node-01 pcs]# 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@r8-node-01 pcs]# 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@r8-node-01 pcs]# pcs property config cluster-name
Cluster Properties:
 cluster-name: HACluster

[root@r8-node-01 pcs]# 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@r8-node-01 pcs]# 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

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

Comment 2 Michal Pospisil 2022-11-24 16:52:50 UTC

DevTestResults:

[root@r08-08-a ~]# rpm -q pcs
pcs-0.10.15-1.el8.x86_64

[root@r08-08-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', '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-bas
e', '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-s
top', '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@r08-08-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', '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-bas
e', '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-s
top', '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

pcs property config cluster-name
Cluster Properties:
cluster-name: onenode

[root@r08-08-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', '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-bas
e', '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-s
top', '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@r08-08-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', '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-bas
e', '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-s
top', '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@r08-08-a ~]# pcs property config cluster-name
Cluster Properties:
cluster-name: onenode

Comment 6 Michal Mazourek 2022-12-09 15:48:16 UTC

BEFORE:
=======

[root@virt-008 ~]# rpm -q pcs
pcs-0.10.14-5.el8.x86_64


[root@virt-008 ~]# pcs property config cluster-name
Cluster Properties:
 cluster-name: STSRHTS318
[root@virt-008 ~]# pcs property set cluster-name=test
[root@virt-008 ~]# pcs property config cluster-name
Cluster Properties:
 cluster-name: test
[root@virt-008 ~]# pcs status | grep name
Cluster name: STSRHTS318


AFTER:
======

[root@virt-516 ~]# rpm -q pcs
pcs-0.10.15-1.el8.x86_64


[root@virt-516 ~]# pcs property config cluster-name
Cluster Properties:
 cluster-name: STSRHTS16992
[root@virt-516 ~]# pcs status | grep name
Cluster name: STSRHTS16992


## trying to set and unset cluster-name property

[root@virt-516 ~]# pcs property set cluster-name=test
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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config cluster-name
Cluster Properties:
 cluster-name: STSRHTS16992

> OK


[root@virt-516 ~]# 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config cluster-name
Cluster Properties:
 cluster-name: STSRHTS16992

> OK


## trying to set and unset cluster-name property with --force

[root@virt-516 ~]# pcs property set cluster-name=test --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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config cluster-name
Cluster Properties:
 cluster-name: STSRHTS16992

> OK


[root@virt-516 ~]# 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
[root@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config cluster-name
Cluster Properties:
 cluster-name: STSRHTS16992

> OK


## trying to set and unset dc-version

[root@virt-516 ~]# pcs property config dc-version
Cluster Properties:
 dc-version: 2.1.5-2.el8-631339ca5aa

[root@virt-516 ~]# pcs property set dc-version=1.2
Error: invalid cluster property option 'dc-version', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config dc-version
Cluster Properties:
 dc-version: 2.1.5-2.el8-631339ca5aa

[root@virt-516 ~]# pcs property set dc-version=1.2 --force
Error: invalid cluster property option 'dc-version', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config dc-version
Cluster Properties:
 dc-version: 2.1.5-2.el8-631339ca5aa

[root@virt-516 ~]# pcs property unset dc-version
Error: invalid cluster property option 'dc-version', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config dc-version
Cluster Properties:
 dc-version: 2.1.5-2.el8-631339ca5aa

> OK


## Trying to set/unset cluster-infrastructure

[root@virt-516 ~]# pcs property config cluster-infrastructure
Cluster Properties:
 cluster-infrastructure: corosync

[root@virt-516 ~]# pcs property set cluster-infrastructure=test
Error: invalid cluster property option 'cluster-infrastructure', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config cluster-infrastructure
Cluster Properties:
 cluster-infrastructure: corosync

[root@virt-516 ~]# pcs property set cluster-infrastructure=test --force
Error: invalid cluster property option 'cluster-infrastructure', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config cluster-infrastructure
Cluster Properties:
 cluster-infrastructure: corosync

[root@virt-516 ~]# pcs property unset cluster-infrastructure 
Error: invalid cluster property option 'cluster-infrastructure', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config cluster-infrastructure
Cluster Properties:
 cluster-infrastructure: corosync

> OK


## Trying to set/unset have-watchdog (which is set automatically by cluster, when required)

[root@virt-516 ~]# pcs property config have-watchdog
Cluster Properties:
 have-watchdog: false

[root@virt-516 ~]# pcs property set have-watchdog=true
Error: invalid cluster property option 'have-watchdog', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config have-watchdog
Cluster Properties:
 have-watchdog: false

[root@virt-516 ~]# pcs property set have-watchdog=true --force
Error: invalid cluster property option 'have-watchdog', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config have-watchdog
Cluster Properties:
 have-watchdog: false

[root@virt-516 ~]# pcs property unset have-watchdog
Error: invalid cluster property option 'have-watchdog', 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@virt-516 ~]# echo $?
1
[root@virt-516 ~]# pcs property config have-watchdog
Cluster Properties:
 have-watchdog: false

> OK


Setting all valid properties with valid and invalid values will be tested in bz2112002.
Marking as Verified for pcs-0.10.15-1.el8.

Comment 11 errata-xmlrpc 2023-05-16 08:12:42 UTC

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:2738