Bug 999630
| Summary: | [RHEVM-ENGINE] Host selection is override if host can't run VM | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Barak Dagan <bdagan> | ||||
| Component: | ovirt-engine | Assignee: | Gilad Chaplik <gchaplik> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.2.0 | CC: | acathrow, alukiano, dfediuck, gchaplik, iheim, lpeer, mavital, pstehlik, Rhev-m-bugs, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | sla | ||||||
| Fixed In Version: | is18 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
In 3.3 there is another scenario - host selection in run once 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 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] 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. Verified on is19, after that I choose host for migration I stop vdsm, so migration failed and vm stay on old host Did you get an event log message explaining that there is a problem with destination host, therefore the migration was canceled ? I just receive message that migration failed but I used second possibility, killed host network where I try migrate my vm Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released |
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: