Cause: When selecting promotable clone instances for promotion on guest nodes, Pacemaker considered whether the guest node itself could run resources, but not whether the guest resource creating it was runnable.
Consequence: An unrunnable guest could be chosen for promotion, unnecessarily leaving some instances unpromoted until the next natural transition.
Fix: Pacemaker now considers whether a guest node's guest resource is runnable when selecting nodes for promotion.
Result: All instances that can be promoted will be.
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 (pacemaker 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-2021:1278
Verified, (undercloud) [stack@undercloud-0 ~]$ ansible controller -b -mshell -a'pcs cluster status'|grep version [WARNING]: Found both group and host with same name: undercloud * Current DC: controller-2 (version 2.0.3-5.el8_2.4-4b1f869f0f) - partition with quorum * Current DC: controller-2 (version 2.0.3-5.el8_2.4-4b1f869f0f) - partition with quorum * Current DC: controller-2 (version 2.0.3-5.el8_2.4-4b1f869f0f) - partition with quorum [root@controller-0 ~]# pcs status|grep ocf::ovn * ovn-dbs-bundle-0 (ocf::ovn:ovndb-servers): Master controller-2 * ovn-dbs-bundle-1 (ocf::ovn:ovndb-servers): Slave controller-1 * ovn-dbs-bundle-2 (ocf::ovn:ovndb-servers): Slave controller-0 [root@controller-0 ~]# pcs status|grep ocf::ovn * ovn-dbs-bundle-0 (ocf::ovn:ovndb-servers): Stopped * ovn-dbs-bundle-1 (ocf::ovn:ovndb-servers): Master controller-1 * ovn-dbs-bundle-2 (ocf::ovn:ovndb-servers): Slave controller-0