Bug 690095

Summary:	Request to remove limitation that fence_scsi requires clvm
Product:	Red Hat Enterprise Linux 5	Reporter:	Satoru SATOH <ssato>
Component:	cman	Assignee:	Lon Hohberger <lhh>
Status:	CLOSED NEXTRELEASE	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.8	CC:	cluster-maint, edamato
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-09 17:04:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	807971

Description Satoru SATOH 2011-03-23 10:56:04 UTC

Description of problem:

fence_scsi requires that all shared storage must use LVM2 cluster volumes.

This constraint does not feel reasonable for me and perhaps looks strange
if there are only fs (not shared mounted fs) resources on these shared storage. 

Also, this constraint increases configuration complexity and maintenance cost,
IMHO.


Instead, how about adding an option to allow users to specify scsi devices
to block explicitly in cluster.conf (e.g. //cluster/fencedevices/failoverdomain[@agent='scsi_fence']/@devices) and
make fence_scsi and scsi_reserve can get the list of all target scsi
devices from cluster.conf ?


I don't have any iSCSI storage devices support SCSI-3 PR so that have not
tested and am not familiar with perl at all but post a kind of concept
patch to eliminate this constraint from fence_scsi.pl and scsi_reserve.


Version-Release number of selected component (if applicable):
cman-2.0.115-68.el5


Additional info:

This constraint was removed in fence_scsi in RHEL6.

Comment 4 RHEL Program Management 2012-04-02 10:52:48 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 Lon Hohberger 2012-04-09 17:04:52 UTC

This feature is addressed in RHEL 6