Bug 1078553 - After host power outage HA vms, failed to run first time because ACTION_TYPE_FAILED_VDS_VM_MEMORY
Summary: After host power outage HA vms, failed to run first time because ACTION_TYPE_...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.4.0
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
: 3.4.0
Assignee: Arik
QA Contact: Artyom
URL:
Whiteboard: virt
Depends On:
Blocks: rhev3.4snapshot2
TreeView+ depends on / blocked
 
Reported: 2014-03-19 22:11 UTC by Artyom
Modified: 2014-06-12 14:08 UTC (History)
12 users (show)

Fixed In Version: av5
Doc Type: Bug Fix
Doc Text:
Previously, the host's committed memory was not cleared immediately after power outage. This meant that it was not possible to run VMs on the host immediately after power outages if the committed memory of the host was high when it was up. If there were highly-available VMs running on the host and there is no other active host in the cluster, failure to restart them meant that they were not restarted automatically. Now, committed memory of hosts is calculated before we try to restart highly available VMs that were running on it before it crashed. When the only active host in a cluster crashes due to power outage, highly-available VMs running on it are now automatically restarted when the host is rebooted.
Clone Of:
Environment:
Last Closed:
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
engine.log (116.47 KB, text/x-log)
2014-03-19 22:11 UTC, Artyom 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25943 0 None None None Never
oVirt gerrit 25953 0 None None None Never

Description Artyom 2014-03-19 22:11:12 UTC 
Created attachment 876652 [details]
engine.log

Description of problem:
I have one host with 16Gb and I run on it 4 HA vms 3 with 4096Mb and 1 with 2048Mb vms started and runs fine.
After it I poweroff host, wait 5 minutes and power on host, vms failed to start first time:
CanDoAction of action RunVm failed. Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_VDS_VM_MEMORY,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName aqua-vds2.qa.lab.tlv.redhat.com,$filterName Memory,SCHEDULING_HOST_FILTERED_REASON 
After it engine try to start HA vms second time and success.

Version-Release number of selected component (if applicable):
av3

How reproducible:
Always

Steps to Reproduce:
1. See above
2.
3.

Actual results:
Engine failed to start HA vms first time because memory filter

Expected results:
Engine success to start HA vms first time, without any error in engine log


Additional info:
Bug also exist in 3.3(checked for is35) and it more critical, because after first failed, engine not try to start HA vms second time
Comment 1 Arik 2014-03-23 12:06:10 UTC 
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=26ad752082943121e9197d9865362359650b491c
Comment 2 Artyom 2014-03-31 15:24:35 UTC 
Verified on rhevm-3.4.0-0.12.beta2.el6ev.noarch
Comment 3 Itamar Heim 2014-06-12 14:08:57 UTC 
Closing as part of 3.4.0
Note You need to log in before you can comment on or make changes to this bug.