Created attachment 493568 [details] related cluster.conf Description of problem: I set a (Xen) vm service to have <vm ... recovery="restart" max_restarts="2" restart_expire_time="600" />, which is part of a two-node ordered failover domain. When I repeatedly crash the guest using 'echo c > /proc/sysrq-trigger', the VM is restarted reliably, but always on the node it was last running on. Version-Release number of selected component (if applicable): cman-2.0.115-68.el5 rgmanager-2.0.52-9.el5 How reproducible: 100% Steps to Reproduce: 1. Create a two-node cluster with a vm service in an ordered failover domain. 2. Crash the VM sufficient times to exceed the maximum restart counting within the restart recovery time. 3. VM will not migrate. Actual results: VM always restarts, doesn't relocate. Expected results: To relocate when limits are exceeded. Additional info: Attached very slightly modified cluster.conf.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.