A managed resource does not failover after failing monitor and stop operations when using 'op stop on-fail=block' in a RHEL 6 or 7 High Availability cluster

Solution In Progress - Updated -

Issue

  • Our postgres resource failed a monitor check, then wasn't running on either node. What should have happened is the primary system should move over the resources to the secondary node. And if it had issues doing so, it would move the resources over and then fence itself or have the secondary node fence the (bad) Primary node
  • Why didn't my resource failover when I have op stop on-fail=block?
  • A monitor check on our resource failed, and the cluster then didn't ever fail it over to another node

Environment

  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add-On
  • pacemaker
  • A resource with op stop on-fail=block set

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.