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 1935240 - pacemaker never promotes a bundle until another transition unblocks it [rhel-8.3.0.z]
Summary: pacemaker never promotes a bundle until another transition unblocks it [rhel-...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.2
Hardware: All
OS: All
high
high
Target Milestone: rc
: ---
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1835717
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-04 14:53 UTC by RHEL Program Management Team
Modified: 2021-04-06 14:07 UTC (History)
8 users (show)

Fixed In Version: pacemaker-2.0.4-6.el8_3.2
Doc Type: Bug Fix
Doc Text:
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.
Clone Of: 1835717
Environment:
Last Closed: 2021-04-06 14:07:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:1088 0 None None None 2021-04-06 14:07:37 UTC

Comment 5 pkomarov 2021-03-21 12:17:33 UTC 
Verified , 

[stack@undercloud-0 ~]$ ansible controller -b -mshell -a'rpm -qa|grep pacemaker-2'
[WARNING]: Found both group and host with same name: undercloud
[WARNING]: Consider using the yum, dnf or zypper module rather than running 'rpm'.  If you need to use command because yum, dnf or zypper is insufficient you can add 'warn: false' to this
command task or set 'command_warnings=False' in ansible.cfg to get rid of this message.
controller-0 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64
controller-1 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64
controller-2 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64

[root@controller-0 ~]# pcs status |grep ovn
  * GuestOnline: [ galera-bundle-0@controller-0 galera-bundle-1@controller-1 galera-bundle-2@controller-2 ovn-dbs-bundle-0@controller-0 ovn-dbs-bundle-1@controller-1 ovn-dbs-bundle-2@controller-2 rabbitmq-bundle-0@controller-0 rabbitmq-bundle-1@controller-1 rabbitmq-bundle-2@controller-2 redis-bundle-0@controller-0 redis-bundle-1@controller-1 redis-bundle-2@controller-2 ]
  * Container bundle set: ovn-dbs-bundle [cluster.common.tag/rhosp16-openstack-ovn-northd:pcmklatest]:
    * ovn-dbs-bundle-0  (ocf::ovn:ovndb-servers):        Master controller-0
    * ovn-dbs-bundle-1  (ocf::ovn:ovndb-servers):        Slave controller-1
    * ovn-dbs-bundle-2  (ocf::ovn:ovndb-servers):        Slave controller-2

[root@controller-0 ~]# pcs resource ban ovn-dbs-bundle controller-0
Warning: Creating location constraint 'cli-ban-ovn-dbs-bundle-on-controller-0' with a score of -INFINITY for resource ovn-dbs-bundle on controller-0.
        This will prevent ovn-dbs-bundle from running on controller-0 until the constraint is removed
        This will be the case even if controller-0 is the last node in the cluster
[root@controller-0 ~]# crm_mon
[root@controller-0 ~]# pcs status |grep ovn
  * Last change:  Sun Mar 21 12:11:37 2021 by ovn-dbs-bundle-1 via crm_attribute on controller-1
  * GuestOnline: [ galera-bundle-0@controller-0 galera-bundle-1@controller-1 galera-bundle-2@controller-2 ovn-dbs-bundle-1@controller-1 ovn-dbs-bundle-2@controller-2 rabbitmq-bundle-0@controller-0 rabbitmq-bundle-1@controller-1 rabbitmq-bundle-2@controller-2 redis-bundle-0@controller-0 redis-bundle-1@controller-1 redis-bundle-2@controller-2 ]
  * Container bundle set: ovn-dbs-bundle [cluster.common.tag/rhosp16-openstack-ovn-northd:pcmklatest]:
    * 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-2
Comment 10 errata-xmlrpc 2021-04-06 14:07:34 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 (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:1088
Note You need to log in before you can comment on or make changes to this bug.