Bug 753839 - fence_scsi: limitations in man page are incorrect
Summary: fence_scsi: limitations in man page are incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cman
Version: 5.8
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ryan O'Hara
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-14 16:27 UTC by Ryan O'Hara
Modified: 2013-01-08 03:36 UTC (History)
5 users (show)

Fixed In Version: cman-2.0.115-100.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-08 03:36:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Remove "limitations" section from man page. (645 bytes, patch)
2012-04-17 23:49 UTC, Ryan O'Hara
no flags Details | Diff
Remove limitations section from man page (1.02 KB, patch)
2012-04-18 00:10 UTC, Ryan O'Hara
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0076 0 normal SHIPPED_LIVE cman bug fix and enhancement update 2013-01-08 08:27:31 UTC

Description Ryan O'Hara 2011-11-14 16:27:57 UTC
The fence_scsi man page in RHEL5 is incorrect. It states:

"The fence_scsi fencing agent requires a minimum of three nodes in the cluster to operate. For SAN devices connected via fiber channel, these must be physical nodes. SAN devices connected via iSCSI may use virtual or physical nodes. In addition, fence_scsi cannot be used in conjunction with qdisk."

There are two things are are incorrect:

1. The fence_scsi agent can be used with two node clusters in 5.4.z and later.
2. The fence_scsi agent can be used with qdisk as long at the qdisk devices are not clvmd devices and therefore subject to SCSI-PR.

I suggest we simply remove this "limitations" section. The correct limitations are well defined in the tech brief.

Comment 2 Ryan O'Hara 2012-04-17 23:49:55 UTC
Created attachment 578188 [details]
Remove "limitations" section from man page.

Most of the limitations listed in the man page were inaccurate. Since the limitations for fence_scsi are documented elsewhere, we can remove them from the man page.

Comment 3 Ryan O'Hara 2012-04-18 00:10:48 UTC
Created attachment 578195 [details]
Remove limitations section from man page

Comment 4 RHEL Program Management 2012-04-18 00:26:56 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 5 Steven J. Levine 2012-04-19 16:37:53 UTC
Setting docs_scoped to +. The updated limitations are already in the Cluster Administration manual, consistent with the tech brief, so there is no further documentation impact.

Comment 6 Steven J. Levine 2012-04-19 16:44:17 UTC
Resetting docs_scoped (to unset), which is what I should have left it as.

Comment 8 michal novacek 2012-07-25 12:18:07 UTC
I have verified that the paragraph is no longer present in the man page in corrected version of rpm.

---

Bugged version: cman-2.0.115-96.el5
Installed corrected version: cman-2.0.115-101.el5

---

# rpm -q cman
cman-2.0.115-101.el5
# diff /usr/share/man/man8/fence_scsi.8.gz ./cman-2.0.115-96.el5/usr/share/man/man8/fence_scsi.8.gz 
101a102,108
> .SH LIMITATIONS
> The fence_scsi fencing agent requires a minimum of three nodes in the
> cluster to operate.  For SAN devices connected via fiber channel,
> these must be physical nodes.  SAN devices connected via iSCSI may use
> virtual or physical nodes.  In addition, fence_scsi cannot be used in
> conjunction with qdisk.
>

Comment 10 errata-xmlrpc 2013-01-08 03:36:48 UTC
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-0076.html


Note You need to log in before you can comment on or make changes to this bug.