RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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