+++ This bug was initially created as a clone of Bug #231241 +++ Description of problem: Fence_xvm and fence_xvmd do not correctly use the contents of /etc/cluster/fence_xvm.key. If multiple clusters are run on the same subnet without the multicast packets being filtered, then it is possible for the following to occur: * If another cluster has a virtual machine with the same name, it can inadvertently fence the virtual machine. * Due to a previous behavioral change, fence_xvmd now returns success if it has never heard of the domain. Both lead to false-success scenarios where a virtual machine has not been correctly fenced. It may be advantageous to give the virtual machine cluster the name or ID of its parent (host) cluster in order to prevent these behaviors from occurring when no authentication is used. -- Additional comment from lhh on 2007-03-06 17:47 EST -- Created an attachment (id=149400) Fixes behavior
Created attachment 149404 [details] fix