Bug 1529967
| Summary: | Live migration doesn't consider over commit ratio | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | David Hill <dhill> |
| Component: | openstack-nova | Assignee: | Matthew Booth <mbooth> |
| Status: | CLOSED ERRATA | QA Contact: | Archit Modi <amodi> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.0 (Liberty) | CC: | amodi, asoni, berrange, ccollett, dasmith, dhill, eglynn, jhakimra, kchamart, mbooth, sbauza, sferdjao, sgordon, srevivo, vromanso |
| Target Milestone: | zstream | Keywords: | Triaged, ZStream |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-nova-12.0.6-22.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when doing a live migration to a destination compute host with RAM overcommit enabled, a pre-live migration check did not consider the configured overcommit ratio when deciding if enough RAM was available.
Consequently, the live migration would fail with the following error in the logs:
"MigrationPreCheckError: Migration pre-check error: Unable to migrate <instance uuid> to <destination host>: Lack of memory(host:336 <= instance:512)"
With this update, the pre-live migration check has been updated to take configured overcommit into account. As a result, the live migration will now succeed as long as the destination compute will not exceed the configured overcommit ratio.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-15 12:35:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Hill
2017-12-31 14:22:26 UTC
This bug is relevant to OSP8, its dependencies are met there, and it backports cleanly. The fix is already present in OSP9 onwards. 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. https://access.redhat.com/errata/RHBA-2018:0529 |