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

Solution Unverified - Updated -

Issue

  • pcs has trouble starting or stopping a group with a VirtualDomain resource in it, if that resource corresponds to a remote-node
  • When I use pcs cluster stop to stop a node, the VM managed by a VirtualDomain resource thats in a group is left running.
  • pcs resource disable on a group with a remote resource or VirtualDomain resource that has a remote-node doesn'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:remote resource, or
      • An ocf:heartbeat:VirtualDomain resource that has the remote-node attribute specified
    • Either the remote resource or VirtualDomain resource belongs to a resource group

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.