resources that return "not installed" from a monitor operation before their dependent resources are active cannot be started in a RHEL 6 High Availability pacemaker cluster

Solution Unverified - Updated -

Issue

  • When we add a mysql resource in a pacemaker cluster, the other nodes in the cluster report that the mysqld binary is not found and reports "Not installed" which prevents the mysql resource from starting on those nodes.
  • If a resource depends on another (such as a Filesystem) before it can be found or used, then pacemaker will report "not installed" errors for it on startup and we can never enable the group its in

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • pacemaker
  • A resource that depends on another resource before it can be activated
    • This is usually true for resources where the binary or some critical file is installed on a shared storage resource like a Filesystem

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