Failure and recovery of a guest remote-node leaves dependencies running on two nodes in a RHEL 7 High Availability cluster

Solution Unverified - Updated -

Issue

  • In our configurations, with VG, FS (for qcow2 & xml) and VMs, if you test a poweroff inside the VM, there is a transitional period where VG is activated on both nodes, FS linked to the VG are mounted on both sides, until pacemaker detect that these resources are activated on both nodes whereas they should be activated on one node (despite the “exclusive” parameter and all the constraints between these resources).
  • If our guest remote-node's container resource - the VirtualDomain - fails and relocates, the other resources it is tied to through constraints end up starting on both nodes, and the Filesystem gets corrupted

Environment

  • Red Hat Enterprise Linux (RHEL) 7 with the High Availability Add-On
  • pacemaker
  • pacemaker-remote
  • One or more "guest remote nodes" - VirtualDomain resources with a meta attribute remote-node set
    • Such a VirtualDomain is colocated and/or ordered with one or more other resources through constraints

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.