Bug 186971

Summary:	LABEL=<label> is invalid in redhat-config-cluster(-cmd) even though it works in underlying system
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Tarun Reddy <tvr1>
Component:	redhat-config-cluster	Assignee:	Ryan McCabe <rmccabe>
Status:	CLOSED WONTFIX	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	3	CC:	cfeist, cluster-maint, jplans
Target Milestone:	rc
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-01-04 20:37:54 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:

Description Tarun Reddy 2006-03-27 19:26:39 UTC

Description of problem:
While the core components of RHCS support mounting via LABEL,
redhat-config-cluster does not accept these values under Device Special File.

Editing the cluster.xml file to place LABEL entries works. This seems like it is
a simple GUI fix to allow LABEL entries for Device mounts.

Version-Release number of selected component (if applicable):
redhat-config-cluster-1.0.8-1

How reproducible:
Always

Steps to Reproduce:
1. Create a filesystem with a label (mkfs.ext3 -L testLabel /dev/sdd
2. open redhat-cluster-config and create a new service.
3. add a device child. Use LABEL=testLabel as the Device Special File. Press OK.
Get error. (put /dev/sdd in for now)
4. Editing cluster.xml by hand to replace /dev/sdd with LABEL=<label> works.
  
Additional info:
redhat-cluster-config-cmd works in the same broken way when attempting to add a
device by LABEL. For example, 
[root@boulder2 root]# redhat-config-cluster-cmd --service=boulder-testmount
--add_device --name="LABEL=/oradata" 
Error: Device Special File "LABEL=/oradata" does not exist

Comment 3 Chris Feist 2009-07-29 17:08:41 UTC

Pulling the 4.8.z flag as this won't be fixed until 4.9 (at the earliest).

Comment 5 RHEL Program Management 2010-01-04 20:37:54 UTC

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.