Bug 967826 - The vm migration should be prevented after changing settings in "resilience policy" of the cluster
Summary: The vm migration should be prevented after changing settings in "resilience p...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact:
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-28 11:47 UTC by Xuesong Zhang
Modified: 2016-02-10 20:17 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-28 20:20:32 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Xuesong Zhang 2013-05-28 11:47:26 UTC
Description of problem:
After changing "Resilience policy" of cluster to "Do not migrate virtual machines", the vm still can be migrating.

Version-Release number of selected component (if applicable):
libvirt-0.10.2-18.el6_4.5
rhevm-3.2.0-10.14.beta1.el6ev.noarch
qemu-kvm-rhev-0.12.1.2-2.355.el6_4.2
spice-server-0.12.0-12.el6
vdsm-4.10.2-1.13.el6ev
kernel-2.6.32-358.2.1.el6.x86_64


How reproducible:
100%

Steps:
1. prepare one health rhevm env, need to prepare 3 hosts:
host1: rhel+rhevm
host2: rhel+vdsm
host3: rhel+vdsm
2. make sure the vm can be migrated between host2 and host3 via rhevm.
3. edit the cluster which contains host2 and host3, navigate to "resilience policy", select "Do not migrate virtual machines", then save.
4. migarate the vm from host2 to host3, the migaration is still successfull.

Actual results:
as step 4

Expected results:
The migration should be prevented.

Comment 1 Itamar Heim 2013-05-28 20:20:32 UTC
4.2.2.3. Resilience Policy Settings Explained[1]
"The resilience policy sets the virtual machine migration policy in the event of host failure. Virtual machines running on a host that unexpectedly shuts down or is put into maintenance mode are migrated to other hosts in the cluster; this migration is dependent upon your cluster policy."

i.e., this is about hosts moving to non operational, not about manual migrations.

[1] https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.2-Beta/html-single/Administration_Guide/index.html#sect-Explanation_of_Settings_and_Controls_in_the_New_Cluster_and_Edit_Cluster_Windows


Note You need to log in before you can comment on or make changes to this bug.