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

Solution In Progress - Updated -

Issue

  • I have interleave=true set 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=true in its instance_attributes in the CIB, but not in its meta_attributes. See the Diagnostic Steps below to check this.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content