Bug 706557

Summary:	can't define VM service with sibling resources
Product:	Red Hat Enterprise Linux 6	Reporter:	joshua
Component:	luci	Assignee:	Ryan McCabe <rmccabe>
Status:	CLOSED NOTABUG	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	cluster-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-20 23:57:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description joshua 2011-05-20 22:37:34 UTC

Description of problem:

When defining a VM as a cluster service, I can't specify another child/parent/sibling resource of a GFS2 filesystem.  This is tricky, because my VM lives in files *on a GFS2* filesystem!  I've had the VM service fail to start a few times on nodes when no other services (where I could define a GFS2 resource) were on that cluster node, such that the GFS2 filesystem wasn't mounted. 

Surely this is a mistake in luci's design!  A VM might actually need other resources as part of its cluster service definition!



Version-Release number of selected component (if applicable):

RHEL 6.1 everything

Comment 2 Ryan McCabe 2011-05-20 23:57:05 UTC

VMs cannot have children. VMs aren't a resource, as such. They're a type of entity on par with services as far as rgmanager is concerned, so different rules apply. There's more info in the rgmanager man page.