Colocation constraint scores on resource groups do not work correctly with default resource-stickiness in a Pacemaker cluster
Issue
- A colocation constraint with a score lower than the default
resource-stickiness
value still overrides the resource stickiness and causes colocation. - Colocation constraints don't work correctly on resource groups with more than four members in a cluster with
resource-stickiness
configured. - Colocation constraint scores aren't treated the same way as location constraint scores.
Environment
- Red Hat Enterprise Linux 7 and higher(with the High Availability Add-on)
- Pacemaker
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.