DevTestResults:

[root@r09-00-a ~]# export NODELIST=(r09-00-a r09-00-b)
pcs host auth -u hacluster -p $PASSWORD ${NODELIST[*]}
pcs cluster setup HACluster ${NODELIST[*]} --start --wait
for node in ${NODELIST[*]}; do
   pcs stonith create fence-1-$node fence_xvm;
done
for node in ${NODELIST[*]}; do
   pcs stonith create fence-2-$node fence_xvm;
done
for node in ${NODELIST[*]}; do
   pcs stonith level add 1 $node fence-1-$node;
   pcs stonith level add 2 $node fence-2-$node;
done
pcs resource create p-1 ocf:pacemaker:Dummy --no-default-ops
pcs resource create p-2 ocf:pacemaker:Dummy --no-default-ops
pcs constraint location p-1 prefers ${NODELIST[0]}
pcs constraint location p-2 avoids ${NODELIST[0]}
pcs resource create s-1 ocf:pacemaker:Stateful promotable --no-default-ops
pcs constraint location s-1-clone rule role=master "#uname" eq ${NODELIST[0]}
pcs resource create oc-1 ocf:pacemaker:Dummy --no-default-ops
pcs resource create oc-2 ocf:pacemaker:Dummy --no-default-ops
pcs constraint order oc-1 then oc-2
pcs constraint colocation add oc-2 with oc-1
pcs resource create oc-set-1 ocf:pacemaker:Dummy --no-default-ops
pcs resource create oc-set-2 ocf:pacemaker:Dummy --no-default-ops
pcs constraint order set oc-set-1 oc-set-2
pcs constraint colocation set oc-set-2 oc-set-1
pcs resource create t ocf:pacemaker:Dummy --no-default-ops
pcs constraint ticket add Ticket t
pcs constraint ticket set p-1 p-2 setoptions ticket=Ticket-set
pcs alert create path=/usr/bin/true id=Alert
pcs alert recipient add Alert value=recipient-value  
pcs resource defaults resource-stickiness=2
pcs resource op defaults timeout=90
pcs property set maintenance-mode=false
pcs tag create TAG p-1 p-2
pcs resource defaults set create id=set-1 meta target-role=Started
pcs resource op defaults set create id=op-set-1 score=10 meta interval=30s
r09-00-a: Authorized
r09-00-b: Authorized
No addresses specified for host 'r09-00-a', using 'r09-00-a'
No addresses specified for host 'r09-00-b', using 'r09-00-b'
Destroying cluster on hosts: 'r09-00-a', 'r09-00-b'...
r09-00-a: Successfully destroyed cluster
r09-00-b: Successfully destroyed cluster
Requesting remove 'pcsd settings' from 'r09-00-a', 'r09-00-b'
r09-00-a: successful removal of the file 'pcsd settings'
r09-00-b: successful removal of the file 'pcsd settings'
Sending 'corosync authkey', 'pacemaker authkey' to 'r09-00-a', 'r09-00-b'
r09-00-a: successful distribution of the file 'corosync authkey'
r09-00-a: successful distribution of the file 'pacemaker authkey'
r09-00-b: successful distribution of the file 'corosync authkey'
r09-00-b: successful distribution of the file 'pacemaker authkey'
Sending 'corosync.conf' to 'r09-00-a', 'r09-00-b'
r09-00-a: successful distribution of the file 'corosync.conf'
r09-00-b: successful distribution of the file 'corosync.conf'
Cluster has been successfully set up.
Starting cluster on hosts: 'r09-00-a', 'r09-00-b'...
Waiting for node(s) to start: 'r09-00-a', 'r09-00-b'...
r09-00-a: Cluster started
r09-00-b: Cluster started
Deprecation Warning: Role value 'master' is deprecated and should not be used, use 'Promoted' instead
Adding oc-1 oc-2 (kind: Mandatory) (Options: first-action=start then-action=start)
Deprecation 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
Deprecation 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
Warning: Defaults do not apply to resources which override them with their own defined values
Warning: Defaults do not apply to resources which override them with their own defined values

[root@r09-00-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 interval=10s timeout=20s (p-1-monitor-interval-10s)
+  Resource: p-2 (class=ocf provider=pacemaker type=Dummy)
+   Operations: monitor interval=10s timeout=20s (p-2-monitor-interval-10s)
+  Clone: s-1-clone
+   Meta Attrs: promotable=true
+   Resource: s-1 (class=ocf provider=pacemaker type=Stateful)
+    Operations: monitor interval=10s role=Promoted timeout=20s (s-1-monitor-interval-10s)
+                monitor interval=11s role=Unpromoted timeout=20s (s-1-monitor-interval-11s)
+  Resource: oc-1 (class=ocf provider=pacemaker type=Dummy)
+   Operations: monitor interval=10s timeout=20s (oc-1-monitor-interval-10s)
+  Resource: oc-2 (class=ocf provider=pacemaker type=Dummy)
+   Operations: monitor interval=10s timeout=20s (oc-2-monitor-interval-10s)
+  Resource: oc-set-1 (class=ocf provider=pacemaker type=Dummy)
+   Operations: monitor interval=10s timeout=20s (oc-set-1-monitor-interval-10s)
+  Resource: oc-set-2 (class=ocf provider=pacemaker type=Dummy)
+   Operations: monitor interval=10s timeout=20s (oc-set-2-monitor-interval-10s)
+  Resource: t (class=ocf provider=pacemaker type=Dummy)
+   Operations: monitor interval=10s timeout=20s (t-monitor-interval-10s)

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

 Location Constraints:
+   Resource: p-1                                                                                                                                                                                   
+     Enabled on:
+       Node: r09-00-a (score:INFINITY) (id:location-p-1-r09-00-a-INFINITY)
+   Resource: p-2
+     Disabled on:
+       Node: r09-00-a (score:-INFINITY) (id:location-p-2-r09-00-a--INFINITY)
+   Resource: s-1-clone
+     Constraint: location-s-1-clone
+       Rule: role=Promoted score=INFINITY (id:location-s-1-clone-rule)
       Expression: #uname eq r09-00-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:
   Meta Attrs: build-resource-defaults
-     resource-stickiness=1
?                         ^
+     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.2-4.el9_0.3-ada5c3b36e2
+  have-watchdog: false
+  maintenance-mode: false

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

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:1981