Bug 1139031
| Summary: | Hard positive affinity prevent to put host to maintenance | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Artyom <alukiano> | ||||
| Component: | ovirt-engine | Assignee: | Nobody <nobody> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Artyom <alukiano> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.5.0 | CC: | dfediuck, ecohen, gklein, iheim, lpeer, mavital, rbalakri, Rhev-m-bugs, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.6.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | sla | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-04-19 12:30:51 UTC | 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: |
|
||||||
Hard affinity takes precedence over other considerations. If there's a critical reason why this should be fixed please provide and re-open. |
Created attachment 935158 [details] engine.log Description of problem: If I have two vms that runs on the same host, and they also included to hard positive affinity group and I try to put this host to maintenance, operation failed, because engine failed to migrate vms, with ERROR in engine.log: 2014-09-07 18:28:08,447 WARN [org.ovirt.engine.core.bll.InternalMigrateVmCommand] (ajp-/127.0.0.1:8702-3) [6c417bf3] CanDoAction of action InternalMigrateVm failed. Reasons:VAR__ACTION__MIGRATE,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName alma07.qa.lab.tlv.redhat.com,$filterName VmAffinityGroups,$affinityRules ,VAR__DETAIL__AFFINITY_FAILED_POSITIVE,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName rose05.qa.lab.tlv.redhat.com,$filterName VmAffinityGroups,$affinityRules ,VAR__DETAIL__AFFINITY_FAILED_POSITIVE,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL 2014-09-07 18:28:08,447 INFO [org.ovirt.engine.core.bll.InternalMigrateVmCommand] (ajp-/127.0.0.1:8702-3) [6c417bf3] Lock freed to object EngineLock [exclusiveLocks= key: 5d75111e-2a6a-400c-a966-a5ebde5d3ffa value: VM , sharedLocks= ] 2014-09-07 18:28:08,464 ERROR [org.ovirt.engine.core.bll.MaintenanceVdsCommand] (ajp-/127.0.0.1:8702-3) [6c417bf3] ResourceManager::vdsMaintenance - Failed migrating desktop Affinity_VM_1 Version-Release number of selected component (if applicable): rhevm-3.5.0-0.10.master.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Create two vms and run them on the same host 2. Create new hard positive affinity group and add vms to this group 3. Put host, where vms runs to maintenance Actual results: Operation failed, because that migration failed and appear ERROR message in engine.log Expected results: Engine check what reason for migration, if reason maintenance, engine migrate two vms(or more if we have more vms in affinity group) on the same host and if migration failed, because some other reason(memory filter for example) maintenance operation stopped. Additional info: