Bug 500172

Summary:	cman - fence_scsi_test.pl does not check for sg_persist in the path
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Marek Grac <mgrac>
Component:	fence	Assignee:	Marek Grac <mgrac>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	cfeist, cluster-maint, djansa, edamato, tao
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	fence-1.32.68-5.el4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	499871	Environment:
Last Closed:	2011-02-16 16:16:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	499871
Bug Blocks:

Description Marek Grac 2009-05-11 13:52:44 UTC

+++ This bug was initially created as a clone of Bug #499871 +++

Escalated to Bugzilla from IssueTracker

--- Additional comment from tao on 2009-05-08 13:00:20 EDT ---

When running fence_scsi_test.pl (as provided in cman) the script does not check to see if sg_persist is in the user's PATH. This can cause for false negatives when running the script.

For example, a customer ran fence_scsi_test.pl after setting SCSI-3 PGR flags on their storage and it reported 'failure' for all of their shared luns. However, this was due to the fact that the customer did not have the sg3_utils package installed.

I have created a patch, which checks the PATH for the sg_persist command and prints an error, telling the user that they need the sg3_utils package installed.
This event sent from IssueTracker by tdunnon  [SEG - Storage]
 issue 293429

--- Additional comment from pbatkowski on 2009-05-11 08:50:58 EDT ---

Created an attachment (id=343441)
proposed patch

--- Additional comment from mgrac on 2009-05-11 09:51:38 EDT ---

Thanks for patch, I just removed $tool_path as it is not used.

Comment 6 errata-xmlrpc 2011-02-16 16:16:06 UTC

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/RHSA-2011-0266.html