Bug 1074478 - After a power outage two VMs marked as HA failed to start automatically, they were required to be started manually.
Summary: After a power outage two VMs marked as HA failed to start automatically, they...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 3.3.2
Assignee: Gilad Chaplik
QA Contact: Artyom
URL:
Whiteboard: sla
Depends On: 1052024
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-10 10:49 UTC by rhev-integ
Modified: 2019-04-28 09:40 UTC (History)
15 users (show)

Fixed In Version: is35.1
Doc Type: Bug Fix
Doc Text:
Previously, not all highly available virtual machines on a given host would be automatically restarted after that host was restarted or experienced a crash and the memory on the highly available virtual machines consumed most of that available to the host. This was caused by incorrect calculation of the committed memory on the host. Now, the calculation of the committed memory has been corrected so that all highly available virtual machines on a given host will be automatically restarted following a crash or restart of the host.
Clone Of: 1052024
Environment:
Last Closed: 2014-04-09 17:56:41 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0384 0 normal SHIPPED_LIVE rhevm 3.3.2 bug fix update 2014-04-09 21:52:20 UTC
oVirt gerrit 24651 0 None None None Never
oVirt gerrit 25461 0 None None None Never
oVirt gerrit 25566 0 None None None Never
oVirt gerrit 25943 0 None None None Never
oVirt gerrit 25948 0 None None None Never

Comment 2 Artyom 2014-03-18 17:02:31 UTC 
Checked on is35
Add host with 16G, and run on it four HA vms, 3 with 4096MB and one with 2048MB, after it powered off host, wait 5 minutes and power on host, all vms failed to start, because memory filter.
Comment 5 Artyom 2014-03-24 15:53:44 UTC 
Verified on is35.1
dd host with 16G, and run on it four HA vms, 3 with 4096MB and one with 2048MB, after it powered off host, wait 5 minutes and power on host, all vms start fine.
Also test run under 'None' cluster policy
Comment 6 Zac Dover 2014-04-03 02:26:32 UTC 
This bug is currently attached to errata RHBA-2014:17286. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.
Comment 8 errata-xmlrpc 2014-04-09 17:56:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0384.html
Note You need to log in before you can comment on or make changes to this bug.