Cloned resource restarts on active Pacemaker cluster node after unstandby or unfence of inactive node

Solution Verified - Updated -

Issue

  • clvmd and GFS2 Filesystem resources restarted after other node came online.
  • All resources restarted after pcs cluster unstandby.
  • Cloned resource with ordering constraints restarted after taking the other node out of standby.
  • One instance of cloned resource fails over.

Environment

  • Red Hat Enterprise Linux 7 Server (with the High Availability Add-on)

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