Bug 1074478
| Summary: | After a power outage two VMs marked as HA failed to start automatically, they were required to be started manually. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Gilad Chaplik <gchaplik> |
| Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.2.0 | CC: | acathrow, adahms, ahadas, avyadav, dfediuck, gchaplik, iheim, knesenko, lpeer, mavital, pmukhedk, Rhev-m-bugs, sherold, sputhenp, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.3.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sla | ||
| 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.
|
Story Points: | --- |
| Clone Of: | 1052024 | Environment: | |
| Last Closed: | 2014-04-09 17:56:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1052024 | ||
| Bug Blocks: | |||
|
Comment 2
Artyom
2014-03-18 17:02:31 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 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. 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 |