Bug 706557 - can't define VM service with sibling resources
Summary: can't define VM service with sibling resources
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-20 22:37 UTC by joshua
Modified: 2011-05-20 23:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-20 23:57:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.