Description of problem:
Use of persistent scsi reservations requires the starting of a service-- /etc/init.d/scsi_reserve
(provided by cman), but this script requires gethostip, which is typically provided by syslinux. The
syslinux package is not provided on Itanium.
Version-Release number of selected component (if applicable):
RHEL 5.0, cman-2.0.64-1.el5
Install cluster suite on Itanium.
Attempt to configure scsi reservations for fencing.
Steps to Reproduce:
1. attempt to start /etc/init.d/scsi_reserve on itanium system
/etc/init.d/scsi_reserve fails because it cannot find gethostip command, which is provided by syslinux
persistent scsi reservations work as a fence device in cluster suite on RHEL 5
*** Bug 249356 has been marked as a duplicate of this bug. ***
We should remove the use of gethostip completely, thus removing the need for
The trick is finding a logical way to get a unique key for all the nodes in the
cluster to use for reservations. The gethostip tool was useful because it gave a
hex representation of the ip address, which is perfect. A possible replacement
would be the nodeid, which means that nodeid would be required. This isn't an
issue for RHEL5 (since nodeid is required anyway), but we'll have to explicitly
state that nodeid's must be defined in cluster.conf for RHEL4 (4.5+) clusters
that use fence_scsi. This is already required for qdisk so its nothing new.
Sorry, this is a rhel5 bug - adding to 5.2 list.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Changing the title of this bug to more accurately reflect the problem.
Fixed. Completely removed use of IP address as basis for SCSI reservation keys,
since this was causing problems. Instead, the SCSI reservation keys are now
based on the cluster ID and node ID. Specifically, the high 16-bits of the key
will be hex value of the cluster ID and the low 16-bits will be hex value of the
Both the scsi_reserve init script and fence_scsi agent were modified for this
Please note that this fix break compatability with older versions of fence_scsi,
since the new code will not recognize the old key format.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.