Stop ordering constraints with kind=Mandatory are treated as optional in a Pacemaker cluster
Issue
- Mandatory stop ordering constraints are ignored unless both resources already needed to stop. (Note:
kind=Mandatory
is the default if akind
option is not specified.) - If a constraint
stop rsc_A then stop rsc_B
is configured, and thenrsc_B
is banned or disabled, Pacemaker does not forcersc_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.