Bug 999630 - [RHEVM-ENGINE] Host selection is override if host can't run VM
Summary: [RHEVM-ENGINE] Host selection is override if host can't run VM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Gilad Chaplik
QA Contact: Artyom
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-21 18:07 UTC by Barak Dagan
Modified: 2016-02-10 20:13 UTC (History)
10 users (show)

Fixed In Version: is18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
engine log + memloading scripts (29.23 KB, application/x-compressed-tar)
2013-08-21 18:07 UTC, Barak Dagan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 19847 0 None None None Never
oVirt gerrit 19970 0 None None None Never

Description Barak Dagan 2013-08-21 18:07:55 UTC
Created attachment 788952 [details]
engine log + memloading scripts

Description of problem:
When manual VM performed, specifying destination host, and that host can't run vm (for example 100% memory load), the VM will be migrated to a third host (if exists). Need to see what happen if there is no 3rd host.

2nd scenario - start vm which is pinned to overloaded host or host in maintenance mode and there is another host in cludter - wasn't tested.
Need to see what happen if there is no 2nd host.


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

How reproducible:
100%

Steps to Reproduce:
1. Create DC with 3 hosts in a cluster + SD
2. Create and start a VM
3. Load different host memory to ~95%
4. Migrate VM to loaded host

Actual results:
VM migrated to the 3rd host

Expected results:
Operation should fail + notify user that dest host is NA

Additional info:

Comment 1 Barak Dagan 2013-08-21 18:11:42 UTC
In 3.3 there is another scenario - host selection in run once

Comment 2 Artyom 2013-10-16 16:46:54 UTC
I success to migrate vm on host with 96% loading of memory, without any error message(it is maximum that I success to reach), I think host just start to use swap, so if you can you give me some advice how to check this scenario?
Thanks

Comment 3 Artyom 2013-10-16 17:26:22 UTC
also after some time I receive this message:
Available memory of host rose05.qa.lab.tlv.redhat.com [222 MB] is under defined threshold [1024 MB]

Comment 4 Gilad Chaplik 2013-10-17 12:32:37 UTC
before this fix, the VM was migrated to another host (not the specified one). you should fail if you have swap; Barak and I wrote a program that loads the host's memory, maybe you can try that.
another possibility is to remove required network from the dest host, in this case it should fail the migration and not try to migrate to another host like it used to.

Comment 5 Artyom 2013-10-18 11:36:00 UTC
Verified on is19, after that I choose host for migration I stop vdsm, so migration failed and vm stay on old host

Comment 6 Barak Dagan 2013-10-20 07:07:11 UTC
Did you get an event log message explaining that there is a problem with destination host, therefore the migration was canceled ?

Comment 7 Artyom 2013-10-20 07:21:43 UTC
I just receive message that migration failed but I used second possibility, killed host network where I try migrate my vm

Comment 8 Itamar Heim 2014-01-21 22:30:09 UTC
Closing - RHEV 3.3 Released

Comment 9 Itamar Heim 2014-01-21 22:30:09 UTC
Closing - RHEV 3.3 Released

Comment 10 Itamar Heim 2014-01-21 22:33:08 UTC
Closing - RHEV 3.3 Released


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