From 57ac83d4d71c903bbaf88a9b6b88a86916c1767c Mon Sep 17 00:00:00 2001 From: Lee Yarwood Date: Fri, 18 Sep 2020 10:45:21 +0100 Subject: [PATCH] releasenote: Add known issue for bug #1894804 Related-Bug: #1882521 Change-Id: Ib9059dde41b0a07144ffa26552577308b1ffc9e1 --- .../notes/bug-1894804-c03c20cd983c3192.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 releasenotes/notes/bug-1894804-c03c20cd983c3192.yaml diff --git a/releasenotes/notes/bug-1894804-c03c20cd983c3192.yaml b/releasenotes/notes/bug-1894804-c03c20cd983c3192.yaml new file mode 100644 index 0000000000..2ddb716ae3 --- /dev/null +++ b/releasenotes/notes/bug-1894804-c03c20cd983c3192.yaml @@ -0,0 +1,15 @@ +--- +issues: + - | + `bug 1894804`_ documents a known device detachment issue with QEMU + ``4.2.0`` as shipped by the Focal ``20.04`` Ubuntu release. This can lead + to the failure to detach devices from the underlying libvirt domain of an + instance as QEMU never emits the correct ``DEVICE_DELETED`` event to + libvirt. This in turn leaves the device attached within libvirt and + OpenStack Nova while it has been detached from the underlying QEMU process. + Subsequent attempts to detach the device will also fail as it is no longer + found within the QEMU process. + + There is no known workaround within OpenStack Nova to this issue. + + .. _bug 1894804: https://bugs.launchpad.net/qemu/+bug/1894804