Bug 2217850

Summary: 'pcs property config --all' shows duplicated records for some of the properties
Product: Red Hat Enterprise Linux 9 Reporter: Nina Hostakova <nhostako>
Component: pcsAssignee: Miroslav Lisik <mlisik>
Status: ON_QA --- QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: low    
Version: 9.3CC: cluster-maint, idevat, mlisik, mmazoure, mpospisi, omular, tojeline
Target Milestone: rcKeywords: Triaged
Target Release: 9.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.11.6-2.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2218841 (view as bug list) Environment:
Last Closed: 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:    
Bug Blocks: 2218841    
Deadline: 2023-07-17   
Attachments:
Description Flags
proposed fix none

Description Nina Hostakova 2023-06-27 09:42:54 UTC 
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
Comment 1 Tomas Jelinek 2023-06-27 10:25:16 UTC 
The root cause is bz2182383
Comment 3 Miroslav Lisik 2023-07-11 16:10:54 UTC 
Created attachment 1975185 [details]
proposed fix

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 4 Michal Pospisil 2023-07-14 09:57:44 UTC 
DevTestResults:

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

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