Red Hat Bugzilla – Bug 187577
Wrong node getting fenced
Last modified: 2009-04-16 16:11:31 EDT
Description of problem:
On a three node cluster, if I down the heartbeat port on node1, I expect the
other two nodes to detect the missing heartbeat on fence node1. I tried this
and node 2 got fenced instead.
Version-Release number of selected component (if applicable):
Only tried once
Steps to Reproduce:
1. Bring up a three node cluster
2. Use ifdown to disable the ethernet port for node 1's heartbeat connection
3. Observe node 2 getting fenced
Node 2 got fenced
Node 1 should be fenced
bind-9.3.2-16.FC5 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
bind-9.3.2-12.FC5 is the latest version available at fedora.redhat.com. Can
you tell me where I can get the -16 version? Also, could this explain the
problems I am still having calling a bash script for my custom fencing method?
I have not been able to reproduce this problem -- is this still an issue?
No, we have not reproduced this problem and do not consider it an issue.