resource fails to start due to another resource not having yet started when pacemaker first starts in a RHEL 6 or 7 High Availability cluster

Solution Unverified - Updated -

Issue

  • I have an lsb script resource in my cluster config, and it requires that a mountpoint be active before it is started. When pacemaker starts, the script fails to start because the mountpoint is not active in time, and when it tries on the other node it succeeds but is running on the non-preferred node.
  • How can I ensure that a resource is only started after all of its dependencies are started?

Environment

  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
  • One or more resources in the CIB that depends on another resource being active in order to successfully start

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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