'pcs resource enable' does not start a clone resource that was disabled in a RHEL 6 or 7 High Availability cluster with pacemaker

Solution Unverified - Updated -

Issue

  • I have a clone resource that will not start even after I run pcs resource enable on it
  • pcs does not enable both the resource and its parent clone or master, but rather just the one you specify, which can lead to confusion if I disable one and then mistakenly enable the other.

Environment

  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
  • pacemaker
  • pcs
  • One or more clone or multi-state (master/slave) resources
    • One of those resources has been disabled, marking it with meta attribute target-role=Stopped in the configuration

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.