diff options
| author | Brett Milford <brett.milford@canonical.com> | 2022-08-04 16:52:33 +1000 |
|---|---|---|
| committer | Brett Milford <brett.milford@canonical.com> | 2022-08-29 11:05:20 +1000 |
| commit | 9fea934c71d3c2fa7fdd80c67d94e18466c5cf9a (patch) | |
| tree | 4902f5e9579513f828b5223f9298642bdd48ea9e /releasenotes | |
| parent | 89ef050b8c049b9a6f0e2c70408fc93c826c55e0 (diff) | |
| download | nova-9fea934c71d3c2fa7fdd80c67d94e18466c5cf9a.tar.gz | |
Handle "no RAM info was set" migration case
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
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/bug-1982284-libvirt-handle-no-ram-info-was-set-99784934ed80fd72.yaml | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/releasenotes/notes/bug-1982284-libvirt-handle-no-ram-info-was-set-99784934ed80fd72.yaml b/releasenotes/notes/bug-1982284-libvirt-handle-no-ram-info-was-set-99784934ed80fd72.yaml new file mode 100644 index 0000000000..943aa99a43 --- /dev/null +++ b/releasenotes/notes/bug-1982284-libvirt-handle-no-ram-info-was-set-99784934ed80fd72.yaml @@ -0,0 +1,11 @@ +--- +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 |