+++ This bug was initially created as a clone of Bug #409451 +++ Description of problem: I forgot I was using the other nic interface and it took me a lot of debugging before I rememebered to use the correct name [root@taft-04 ~]# fence_scsi -n taft-03 Unable to execute sg_persist (/dev/sdb1). [root@taft-04 ~]# fence_scsi -n taft-03-e2 A message like "taft-03 doesn't exist in this cluster" would be more helpful. Version-Release number of selected component (if applicable): fence-1.32.50-2.fencescsi.test.patch
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 release.
Fixed in RHEL5. As mentioned above, the script will simply check to see the nodeid we get from the XML query of cluster.conf. If nodeid is zero, then either the node does not exist in this cluster or the nodeid is not set. Either case is invalid, so we report and error and exit.
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 therefore 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. http://rhn.redhat.com/errata/RHBA-2009-0189.html