pacemaker: no failover of vm in case of resource failed on remote-node (with our configuration)
Issue
- On each resource running on remote-nodes, we have
op mon on-failed=fenceso that in case of monitoring failed the vm is fenced and restarted. When a resource on remote-node fails, the vm is always restarted locally on the same node and never migrated to a second node. - When a resource running in a remote node fails a monitor operation, and that resource has
op monitor on-fail=fence, that fence of the remote-node does not reflect in thefailcountof the container VM resource.
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add-On
pacemaker- One or more
ocf:heartbeat:VirtualDomainresources with meta attributeremote-nodeset - One or more resources configured to run on a remote-node, also having
op monitor on-fail=fenceset. migration-threshold> 0 on theVirtualDomainresource(s)
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.
