-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Low
-
rhel-ha
-
2
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
As a cluster administrator, I need a clear suggestion to use the pcs cluster rename command when I attempt to change a cluster-name cluster property using pcs property set command, so that I am efficiently guided to the correct procedure and instead of getting a generic error.
Goal
Improve user-friendliness by suggesting to use the command 'pcs cluster rename', when a user attempts to rename the cluster via property (instead of showing a plain error message).
Acceptance criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- When used property to rename cluster, suggest to use 'pcs cluster rename'
Actual behavior
[root@virt-202 ~]# pcs property set cluster-name=A 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', 'node-pending-timeout', 'pe-error-series-max', 'pe-input-series-max', 'pe-warn-series-max', 'placement-strategy', 'priority-fencing-delay', '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