Why my custom resource agent is reported to be running on multiple nodes despite it should run only on one?
Issue
- Why my custom resource agent is reported to be running on multiple nodes despite it should run only on one?
- Why it looks like cluster doesn't distinguish between resources of same custom resource agent type?
Environment
- Red Hat Enterprise Linux 6,7 with High Availability or Resilient Storage Add-on with Pacemaker
- There are multiple resources of custom resource agent in cluster configured to be running either on separate nodes or on single node.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.