Node is evicted from the cluster when creating a vm snapshot in VMware Environment.
Environment
- Red Hat Enterprise Linux
- VMware Virtulization
Issue
- When creating a vm snapshot of a virtual machine that is part of a Red Hat High Availability cluster, the node is evicted from the cluster.
Resolution
Removing the node from the cluster by stopping the cluster services before performing a VMware snapshot of the virtual machine is recommended. Doing so prevents the system from being rebooted while the snapshot occurs as well as potentially corrupting the snapshot itself via a reboot during a snapshot.
Stopping cluster services on a cman cluster
Refer to the following solution: [What order do I need to start/stop the cluster services in?](https://access.redhat.com/solutions/224263#rhel6)
Stopping cluster services on a Pacemaker cluster
# pcs cluster stop
Root Cause
At the time that a VMware snapshot is being created the virtual machine is essentially being frozen. When the virtual machine is frozen it is no longer communicating with the other nodes in the cluster. If the node is frozen longer than the set token timeout, the cluster has effectively lost communication with that node and will fence/evict the node as a result.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.