Bug 2218841

Summary:	'pcs property config --all' shows duplicated records for some of the properties
Product:	Red Hat Enterprise Linux 8	Reporter:	Miroslav Lisik <mlisik>
Component:	pcs	Assignee:	Miroslav Lisik <mlisik>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	low	Docs Contact:
Priority:	low
Version:	8.9	CC:	cluster-maint, idevat, mlisik, mmazoure, mpospisi, nhostako, omular, tojeline
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pcs-0.10.17-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2217850	Environment:
Last Closed:	2023-11-14 15:22:35 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:
Bug Depends On:	2217850
Bug Blocks:

Description Miroslav Lisik 2023-06-30 08:13:37 UTC

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

Description of problem:
Some of the properties are doubled in 'pcs property [config] --all' (as well as in 'pcs property describe'), however in 'pcs property defaults' they are listed only once

Version-Release number of selected component (if applicable):
pcs-0.11.5-1.el9

Steps to Reproduce:
# pcs property --all
Cluster Properties: cib-bootstrap-options
  batch-limit=0 (default)
  cluster-delay=60s (default)
  cluster-infrastructure=corosync
  cluster-ipc-limit=500 (default)
  cluster-name=STSRHTS5196
  cluster-recheck-interval=15min (default)
  concurrent-fencing=true (default)
  dc-deadtime=20s (default)
  dc-version=2.1.6-2.el9-6fdc9deea29
  election-timeout=2min (default)
  enable-acl=false (default)
  enable-startup-probes=true (default)
  fence-reaction=stop (default)
  have-watchdog=false
  join-finalization-timeout=30min (default)
  join-integration-timeout=3min (default)
  load-threshold=80% (default)
  maintenance-mode=false (default)
  migration-limit=-1 (default)
  no-quorum-policy=stop (default)
  no-quorum-policy=stop (default)
  node-action-limit=0 (default)
  node-health-base=0 (default)
  node-health-green=0 (default)
  node-health-red=-INFINITY (default)
  node-health-strategy=none (default)
  node-health-yellow=0 (default)
  pe-error-series-max=-1 (default)
  pe-input-series-max=4000 (default)
  pe-warn-series-max=5000 (default)
  placement-strategy=default (default)
  priority-fencing-delay=0 (default)
  remove-after-stop=false (default)
  shutdown-escalation=20min (default)
  shutdown-lock=false (default)
  shutdown-lock=false (default)
  shutdown-lock-limit=0 (default)
  shutdown-lock-limit=0 (default)
  start-failure-is-fatal=true (default)
  startup-fencing=true (default)
  stonith-action=reboot (default)
  stonith-enabled=true (default)
  stonith-max-attempts=10 (default)
  stonith-timeout=60s (default)
  stonith-watchdog-timeout=0 (default)
  stop-all-resources=false (default)
  stop-orphan-actions=true (default)
  stop-orphan-resources=true (default)
  symmetric-cluster=true (default)
  transition-delay=0s (default)

# pcs property defaults
batch-limit=0
cluster-delay=60s
cluster-infrastructure=corosync
cluster-ipc-limit=500
cluster-recheck-interval=15min
concurrent-fencing=true
dc-deadtime=20s
dc-version=none
enable-acl=false
enable-startup-probes=true
fence-reaction=stop
have-watchdog=false
load-threshold=80%
maintenance-mode=false
migration-limit=-1
no-quorum-policy=stop
node-action-limit=0
node-health-base=0
node-health-green=0
node-health-red=-INFINITY
node-health-strategy=none
node-health-yellow=0
pe-error-series-max=-1
pe-input-series-max=4000
pe-warn-series-max=5000
placement-strategy=default
priority-fencing-delay=0
remove-after-stop=false
shutdown-lock=false
shutdown-lock-limit=0
start-failure-is-fatal=true
stonith-action=reboot
stonith-max-attempts=10
stonith-watchdog-timeout=0
stop-all-resources=false
stop-orphan-actions=true
stop-orphan-resources=true
symmetric-cluster=true

Actual results:
duplicated 'no-quorum-policy', 'shutdown-lock' and 'shutdown-lock-limit' records

--- Additional comment from Tomas Jelinek on 2023-06-27 12:25:16 CEST ---

The root cause is bz2182383

Comment 2 Miroslav Lisik 2023-07-12 14:30:14 UTC

Upstream commit: https://github.com/ClusterLabs/pcs/commit/d441773b1da3392e472cd39891a6ee801b4785e6

Updated commands:
* pcs property [config] --all
* pcs property describe

Enviroment: A running cluster with some configured properties.

Test:
# pcs property config --all | uniq -d | wc -l
0

# pcs property describe --full | grep -v '^[ ]' | uniq -d | wc -l
0

Comment 3 Michal Pospisil 2023-07-14 08:41:24 UTC

DevTestResults:

[root@r08-09-a ~]# pcs property config --all | uniq -d | wc -l
0

[root@r08-09-a ~]# pcs property describe --full | grep -v '^[ ]' | uniq -d | wc -l
0

Comment 10 errata-xmlrpc 2023-11-14 15:22:35 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:6903