Description of problem:
Under some circumsatances 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):
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
under some circumstances both resources end up running on the same node
under no circumstances resources should be running on the same node
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:
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.