Stop ordering constraints with kind=Mandatory are treated as optional in a Pacemaker cluster

Solution In Progress - Updated -

Issue

  • Mandatory stop ordering constraints are ignored unless both resources already needed to stop. (Note: kind=Mandatory is the default if a kind option is not specified.)
  • If a constraint stop rsc_A then stop rsc_B is configured, and then rsc_B is banned or disabled, Pacemaker does not force rsc_A to stop first as it should.

Environment

  • Red Hat Enterprise Linux 6, 7, or 8 (with the High Availability Add-on)
  • Pacemaker

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