Cloned resource restarts on active Pacemaker cluster node after unstandby or unfence of inactive node
Issue
clvmdand GFS2Filesystemresources 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 of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.