9fea934c71
This handles the case where the live migration monitoring thread may
race and call jobStats() after the migration has completed resulting in
the following error:
libvirt.libvirtError: internal error: migration was active, but no
RAM info was set
Closes-Bug: #1982284
Change-Id: I77fdfa9cffbd44b2889f49f266b2582bcc6a4267
12 lines
351 B
YAML
12 lines
351 B
YAML
---
|
|
other:
|
|
- |
|
|
A workaround has been added to the libvirt driver to catch and pass
|
|
migrations that were previously failing with the error:
|
|
|
|
``libvirt.libvirtError: internal error: migration was active, but no RAM info was set``
|
|
|
|
See `bug 1982284`_ for more details.
|
|
|
|
.. _bug 1982284: https://bugs.launchpad.net/nova/+bug/1982284
|