Bug 621694

Summary: Restricted failover domains don't work with VM migrations
Product: Red Hat Enterprise Linux 6 Reporter: Lon Hohberger <lhh>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: alan.staples, cluster-maint, edamato, mmilgram
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rgmanager-3.0.12-11.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 592380 Environment:
Last Closed: 2011-05-19 14:18:12 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 Lon Hohberger 2010-08-05 20:28:17 UTC
+++ This bug was initially created as a clone of Bug #592380 +++

Description of problem:
clusvcadm -M will migrate a VM outside of a failover domain.

Version-Release number of selected component (if applicable):
rgmanager-2.0.52-6.el5.x86_64.rpm

How reproducible:
Every time

Steps to Reproduce:
1. Define a VM service in cluster.conf.
2. Define a restricted failover domain containing a subset of cluster nodes.
3. Start the VM service on one of the failover domain nodes.
4. MIGRATE the VM (clusvcadm -M) to the same non-domain node where you attempted to start it.
  
Actual results:
A VM service in a restricted failover domain can be migrated to a node that is not part of that failover domain.

Expected results:
A VM service in a restricted failover domain should only be able to run on nodes that are part of the failover domain.

Additional info:

Comment 8 errata-xmlrpc 2011-05-19 14:18:12 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/RHBA-2011-0750.html