https://bugzilla.redhat.com/show_bug.cgi?id=570373
And for me it works perfectly if the dom0 is fenced using fence_node on the command line. However, if the host becomes unavailable then it is not fenced, and from reading the fenced man page it seems this is because there isn't a shared resource like clvm or gfs, so therefore the cluster doesn't see a need to fence the host. This means subsequent fence_xvm commands fail.
I guess I need to find a way to force fenced to operate without clvm and fence dom0s?
Joel
On Fri, Oct 1, 2010 at 3:12 PM, Joel Heenan <joelh@xxxxxxxxxxxxxx> wrote:
I'm conducting some HA testing and I found that if I destroy a dom0, the other guest nodes (running on separate dom0s) all try to fence the guest that has disappeared but they fail because they can't reach fence_xvmd (the dom0 is down). They sit there trying to fence forever and never make any progress until the dom0 has rebooted and the guest is back up. This is a lot of downtime.
What I tried was to make a secondary fence_manual after the fence_xen but the problem is that it then requires me to manuall acknowledge fencing.
What I would like is "try fencing, if it fails don't worry just continue as if it succeeded"? Is there an option for this?
Thanks
Joel
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
