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.

+++ This bug was initially created as a clone of Bug #1069279 +++

Description of problem:
Under some circumstances it can happen that two resources end up running on the same node even though a "anti-colocation" rule (colocation rule with score INFINITY) was set up that should prevent this.

Version-Release number of selected component (if applicable):
pacemaker-1.1.10-24.el7

How reproducible:
sometimes

Steps to Reproduce:
1. configure two resources that should always run on different nodes
2. set up colocation rule with score INFINITY to prevent the two resources from running on the same node  
3.

Actual results:
under some circumstances both resources end up running on the same node

Expected results:
under no circumstances resources should be running on the same node

Additional info:
I've not discovered this issue myself, but was informed by a colleague from SUSE about it.

A fix for this is available in the following upstream commit:
https://github.com/ClusterLabs/pacemaker/commit/9f9ed87e01bfafec0ddeee6592eb07e81bef963e

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.