Cluster framework should honor the `migrate` setting of VM resources on failback

Solution Verified - Updated -

Issue

  • If a virtual machine (VM) resource in a cluster has nofailback=0 set to move it back to the original node after recovery, the cluster will always do a relocation of the VM - thus disrupting the service.
  • The virtual machine which was running on a preferred node got restarted instead of being live-migrated after the preferred node rejoined the cluster.

Environment

  • Red Hat Enterprise Linux Server 6 (with the High Availability Add Ons)
  • Virtual machines running as resource in failover_domain
  • central_processing ennabled

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.