pcs resource or cluster operations become blocked or do not behave as expected when a VirtualDomain or remote resource is configured in a resource group in a RHEL 6 or 7 High Availability cluster
Issue
pcshas trouble starting or stopping a group with aVirtualDomainresource in it, if that resource corresponds to aremote-node- When I use
pcs cluster stopto stop a node, the VM managed by aVirtualDomainresource thats in a group is left running. pcs resource disableon a group with a remote resource orVirtualDomainresource that has aremote-nodedoesn't work- There is unexpected behavior in the cluster when a remote-resource or its container belongs to a group
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
pacemaker- One or more remote-nodes that belongs to a resource group in the CIB
- A remote-node entails either:
- An
ocf:pacemaker:remoteresource, or - An
ocf:heartbeat:VirtualDomainresource that has theremote-nodeattribute specified
- An
- Either the
remoteresource orVirtualDomainresource belongs to a resource group
- A remote-node entails either:
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
