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 2180700 - Command 'pcs config checkpoint diff' does not show configuration differences between checkpoints [rhel-8.8.0.z]
Summary: Command 'pcs config checkpoint diff' does not show configuration differences ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Miroslav Lisik
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 2176490
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-22 05:35 UTC by RHEL Program Management Team
Modified: 2023-05-16 11:32 UTC (History)
11 users (show)

Fixed In Version: pcs-0.10.15-4.el8_8.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2176490
Environment:
Last Closed: 2023-05-16 09:59:09 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-152655 0 None None None 2023-03-22 05:38:00 UTC
Red Hat Product Errata RHSA-2023:3082 0 None None None 2023-05-16 09:59:21 UTC

Comment 1 Michal Pospisil 2023-03-31 06:26:07 UTC
DevTestResults:

[root@r08-08-a ~]# export NODELIST=(r08-08-a r08-08-b)

[root@r08-08-a ~]# pcs host auth -u hacluster -p $PASSWORD ${NODELIST[*]}
r08-08-a: Authorized
r08-08-b: Authorized

[root@r08-08-a ~]# pcs cluster setup HACluster ${NODELIST[*]} --start --wait
No addresses specified for host 'r08-08-a', using 'r08-08-a'
No addresses specified for host 'r08-08-b', using 'r08-08-b'
Destroying cluster on hosts: 'r08-08-a', 'r08-08-b'...
r08-08-b: Successfully destroyed cluster
r08-08-a: Successfully destroyed cluster
Requesting remove 'pcsd settings' from 'r08-08-a', 'r08-08-b'
r08-08-a: successful removal of the file 'pcsd settings'
r08-08-b: successful removal of the file 'pcsd settings'
Sending 'corosync authkey', 'pacemaker authkey' to 'r08-08-a', 'r08-08-b'
r08-08-a: successful distribution of the file 'corosync authkey'
r08-08-a: successful distribution of the file 'pacemaker authkey'
r08-08-b: successful distribution of the file 'corosync authkey'
r08-08-b: successful distribution of the file 'pacemaker authkey'
Sending 'corosync.conf' to 'r08-08-a', 'r08-08-b'
r08-08-a: successful distribution of the file 'corosync.conf'
r08-08-b: successful distribution of the file 'corosync.conf'
Cluster has been successfully set up.
Starting cluster on hosts: 'r08-08-a', 'r08-08-b'...
Waiting for node(s) to start: 'r08-08-a', 'r08-08-b'...
r08-08-a: Cluster started
r08-08-b: Cluster started

[root@r08-08-a ~]# for node in ${NODELIST[*]}; do
> 	pcs stonith create fence-1-$node fence_xvm;
> done

[root@r08-08-a ~]# for node in ${NODELIST[*]}; do
> 	pcs stonith create fence-2-$node fence_xvm;
> done

[root@r08-08-a ~]# for node in ${NODELIST[*]}; do
> 	pcs stonith level add 1 $node fence-1-$node;
> 	pcs stonith level add 2 $node fence-2-$node;
> done

[root@r08-08-a ~]# pcs resource create p-1 ocf:pacemaker:Dummy --no-default-ops

[root@r08-08-a ~]# pcs resource create p-2 ocf:pacemaker:Dummy --no-default-ops

[root@r08-08-a ~]# pcs constraint location p-1 prefers ${NODELIST[0]}

[root@r08-08-a ~]# pcs constraint location p-2 avoids ${NODELIST[0]}

[root@r08-08-a ~]# pcs resource create s-1 ocf:pacemaker:Stateful promotable --no-default-ops

[root@r08-08-a ~]# pcs constraint location s-1-clone rule role=master "#uname" eq ${NODELIST[0]}

[root@r08-08-a ~]# pcs resource create oc-1 ocf:pacemaker:Dummy --no-default-ops

[root@r08-08-a ~]# pcs resource create oc-2 ocf:pacemaker:Dummy --no-default-ops

[root@r08-08-a ~]# pcs constraint order oc-1 then oc-2
Adding oc-1 oc-2 (kind: Mandatory) (Options: first-action=start then-action=start)

[root@r08-08-a ~]# pcs constraint colocation add oc-2 with oc-1

[root@r08-08-a ~]# pcs resource create oc-set-1 ocf:pacemaker:Dummy --no-default-ops

[root@r08-08-a ~]# pcs resource create oc-set-2 ocf:pacemaker:Dummy --no-default-ops

[root@r08-08-a ~]# pcs constraint order set oc-set-1 oc-set-2

[root@r08-08-a ~]# pcs constraint colocation set oc-set-2 oc-set-1

[root@r08-08-a ~]# pcs resource create t ocf:pacemaker:Dummy --no-default-ops

[root@r08-08-a ~]# pcs constraint ticket add Ticket t

[root@r08-08-a ~]# pcs constraint ticket set p-1 p-2 setoptions ticket=Ticket-set

[root@r08-08-a ~]# pcs alert create path=/usr/bin/true id=Alert

[root@r08-08-a ~]# pcs alert recipient add Alert value=recipient-value

[root@r08-08-a ~]# pcs resource defaults resource-stickiness=2
Warning: This command is deprecated and will be removed. Please use 'pcs resource defaults update' instead.
Warning: Defaults do not apply to resources which override them with their own defined values

[root@r08-08-a ~]# pcs resource op defaults timeout=90
Warning: This command is deprecated and will be removed. Please use 'pcs resource op defaults update' instead.
Warning: Defaults do not apply to resources which override them with their own defined values

[root@r08-08-a ~]# pcs property set maintenance-mode=false

[root@r08-08-a ~]# pcs tag create TAG p-1 p-2

[root@r08-08-a ~]# pcs resource defaults set create id=set-1 meta target-role=Started
Warning: Defaults do not apply to resources which override them with their own defined values

[root@r08-08-a ~]# pcs resource op defaults set create id=op-set-1 score=10 meta interval=30s
Warning: Defaults do not apply to resources which override them with their own defined values

[root@r08-08-a ~]# pcs config checkpoint diff 1 live
Differences between checkpoint 1 (-) and live configuration (+):
  Resources:
+   Resource: p-1 (class=ocf provider=pacemaker type=Dummy)
+ 	Operations:
+   	monitor: p-1-monitor-interval-10s
+     	interval=10s
+     	timeout=20s
+   Resource: p-2 (class=ocf provider=pacemaker type=Dummy)
+ 	Operations:
+   	monitor: p-2-monitor-interval-10s
+     	interval=10s
+     	timeout=20s
+   Resource: oc-1 (class=ocf provider=pacemaker type=Dummy)
+ 	Operations:
+   	monitor: oc-1-monitor-interval-10s
+     	interval=10s
+     	timeout=20s
+   Resource: oc-2 (class=ocf provider=pacemaker type=Dummy)
+ 	Operations:
+   	monitor: oc-2-monitor-interval-10s
+     	interval=10s
+     	timeout=20s
+   Resource: oc-set-1 (class=ocf provider=pacemaker type=Dummy)
+ 	Operations:
+   	monitor: oc-set-1-monitor-interval-10s
+     	interval=10s
+     	timeout=20s
+   Resource: oc-set-2 (class=ocf provider=pacemaker type=Dummy)
+ 	Operations:
+   	monitor: oc-set-2-monitor-interval-10s
+     	interval=10s
+     	timeout=20s
+   Resource: t (class=ocf provider=pacemaker type=Dummy)
+ 	Operations:
+   	monitor: t-monitor-interval-10s
+     	interval=10s
+     	timeout=20s
+   Clone: s-1-clone
+ 	Meta Attributes: s-1-clone-meta_attributes
+   	promotable=true
+ 	Resource: s-1 (class=ocf provider=pacemaker type=Stateful)
+   	Operations:
+     	monitor: s-1-monitor-interval-10s
+       	interval=10s
+       	timeout=20s
+       	role=Master
+     	monitor: s-1-monitor-interval-11s
+       	interval=11s
+       	timeout=20s
+       	role=Slave

  Stonith Devices:
+   Resource: fence-1-r08-08-a (class=stonith type=fence_xvm)
+ 	Operations:
+   	monitor: fence-1-r08-08-a-monitor-interval-60s
+     	interval=60s
+   Resource: fence-1-r08-08-b (class=stonith type=fence_xvm)
+ 	Operations:
+   	monitor: fence-1-r08-08-b-monitor-interval-60s
+     	interval=60s
+   Resource: fence-2-r08-08-a (class=stonith type=fence_xvm)
+ 	Operations:
+   	monitor: fence-2-r08-08-a-monitor-interval-60s
+     	interval=60s
+   Resource: fence-2-r08-08-b (class=stonith type=fence_xvm)
+ 	Operations:
+   	monitor: fence-2-r08-08-b-monitor-interval-60s
+     	interval=60s
  Fencing Levels:
+   Target: r08-08-a
+ 	Level 1 - fence-1-r08-08-a
+ 	Level 2 - fence-2-r08-08-a
+   Target: r08-08-b
+ 	Level 1 - fence-1-r08-08-b
+ 	Level 2 - fence-2-r08-08-b

  Location Constraints:
+   Resource: p-1
+ 	Enabled on:
+   	Node: r08-08-a (score:INFINITY) (id:location-p-1-r08-08-a-INFINITY)
+   Resource: p-2
+ 	Disabled on:
+   	Node: r08-08-a (score:-INFINITY) (id:location-p-2-r08-08-a--INFINITY)
+   Resource: s-1-clone
+ 	Constraint: location-s-1-clone
+   	Rule: role=Master score=INFINITY (id:location-s-1-clone-rule)
    	Expression: #uname eq r08-08-a (id:location-s-1-clone-rule-expr)
  Ordering Constraints:
+   start oc-1 then start oc-2 (kind:Mandatory) (id:order-oc-1-oc-2-mandatory)
+   Resource Sets:
+ 	set oc-set-1 oc-set-2 (id:order_set_o1o2_set) (id:order_set_o1o2)
  Colocation Constraints:
+   oc-2 with oc-1 (score:INFINITY) (id:colocation-oc-2-oc-1-INFINITY)
+   Resource Sets:
+ 	set oc-set-2 oc-set-1 (id:colocation_set_o2o1_set) setoptions score=INFINITY (id:colocation_set_o2o1)
  Ticket Constraints:
+   t ticket=Ticket (id:ticket-Ticket-t)
+   Resource Sets:
+ 	set p-1 p-2 (id:ticket_set_p1p2_set) setoptions ticket=Ticket-set (id:ticket_set_p1p2)

  Alerts:
-  No alerts defined
+  Alert: Alert (path=/usr/bin/true)
+   Recipients:
+	Recipient: Alert-recipient (value=recipient-value)

  Resources Defaults:
-   No defaults set
+   Meta Attrs: rsc_defaults-meta_attributes
+ 	resource-stickiness=2
+   Meta Attrs: set-1
+ 	target-role=Started
  Operations Defaults:
-   No defaults set
+   Meta Attrs: op_defaults-meta_attributes
+ 	timeout=90
+   Meta Attrs: op-set-1 score=10
+ 	interval=30s

  Cluster Properties:
+  cluster-infrastructure: corosync
+  cluster-name: HACluster
+  dc-version: 2.1.5-8.el8-a3f44794f94
+  have-watchdog: false
+  maintenance-mode: false

  Tags:
-  No tags defined
+  TAG
+	p-1
+	p-2

Comment 9 errata-xmlrpc 2023-05-16 09:59:09 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 (Moderate: pcs security and bug fix 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:3082


Note You need to log in before you can comment on or make changes to this bug.