RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2217850 - 'pcs property config --all' shows duplicated records for some of the properties
Summary: 'pcs property config --all' shows duplicated records for some of the properties
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2023-07-17
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcs
Version: 9.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 9.3
Assignee: Miroslav Lisik
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks: 2218841
TreeView+ depends on / blocked
 
Reported: 2023-06-27 09:42 UTC by Nina Hostakova
Modified: 2023-11-07 08:57 UTC (History)
7 users (show)

Fixed In Version: pcs-0.11.6-2.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2218841 (view as bug list)
Environment:
Last Closed: 2023-11-07 08:23:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (10.69 KB, patch)
2023-07-11 16:10 UTC, Miroslav Lisik 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2182383 0 high CLOSED Both pacemaker-controld and pacemaker-schedulerd metadata contains 'no-quorum-policy' cluster property 2023-09-22 20:10:28 UTC
Red Hat Issue Tracker CLUSTERQE-6798 0 None None None 2023-06-30 14:13:51 UTC
Red Hat Issue Tracker RHELPLAN-160896 0 None None None 2023-06-27 09:44:08 UTC
Red Hat Product Errata RHSA-2023:6316 0 None None None 2023-11-07 08:23:27 UTC

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
Comment 11 errata-xmlrpc 2023-11-07 08:23:11 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 (Low: pcs security, 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/RHSA-2023:6316
Note You need to log in before you can comment on or make changes to this bug.