Red Hat Bugzilla – Bug 887349
fence_scsi man page should mention that configuring respective unfence is more than reasonable
Last modified: 2013-11-21 02:16:57 EST
From a recent discussion about fence_sanlock, it came out that fence_scsi is another example of fence agent requiring unfence configured for a proper function. Contrary to fence_sanlock, fence_scsi man page does not document this. IMHO, any nontrivial restriction leading to nontrivial issues when not abided should be documented. # rpm -qf /usr/share/man/man8/fence_scsi.8.gz fence-agents-3.1.5-17.el6.x86_64
The fence_scsi agent doesn't *require* unfencing, the cluster requires it. In other words, unfencing is a cluster concept. The fence_scsi agent can be used outside of cluster product, in which case unfencing is meaningless. NACK.
Ah, ok. If it is not even recommendable in general (is it?), please close the bug.
Well, the whole man page seems to talk about fence_scsi in the context of cluster, so this bug is completely valid.
Let´s add a note, that when fence_scsi is used in a cluster context, unfecing should be configured/executed. This should make everybody happy.
Fixed in upstream: https://git.fedorahosted.org/cgit/fence-agents.git/commit/?id=d6504496b019dcd6bd066dd398b898b87d4ddd49
I should add a similar note to the Cluster Administration manual so I'm cloning this as a documentation bug.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1562.html