interleave=true does not seem to be respected on a clone resource with an order constraint in a RHEL 6 or 7 High Availability cluster
Issue
- I have
interleave=trueset on a clone resource and have a Mandatory order constraint, but all instances of the resource clone set restart when an instance of the first resource clone set starts or restarts.
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
pacemaker- Two resource clone sets
- The resources are connected through an order constraint
- The order constraint is mandatory
- The "second" resource clone set has
interleave=truein itsinstance_attributesin the CIB, but not in itsmeta_attributes. See the Diagnostic Steps below to check this.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
