summaryrefslogtreecommitdiff
path: root/releasenotes/notes/unplug-vifs-in-resize_instance-fcd98ea44e4b8725.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/unplug-vifs-in-resize_instance-fcd98ea44e4b8725.yaml')
-rw-r--r--releasenotes/notes/unplug-vifs-in-resize_instance-fcd98ea44e4b8725.yaml12
1 files changed, 12 insertions, 0 deletions
diff --git a/releasenotes/notes/unplug-vifs-in-resize_instance-fcd98ea44e4b8725.yaml b/releasenotes/notes/unplug-vifs-in-resize_instance-fcd98ea44e4b8725.yaml
new file mode 100644
index 0000000000..fa88e7a927
--- /dev/null
+++ b/releasenotes/notes/unplug-vifs-in-resize_instance-fcd98ea44e4b8725.yaml
@@ -0,0 +1,12 @@
+---
+fixes:
+ - |
+ Support for cold migration and resize between hosts with different network backends
+ was previously incomplete. If the os-vif plugin for all network backends available
+ in the cloud are not installed on all nodes unplugging will fail during confirming
+ the resize. The issue is caused by the VIF unplug that happened during the resize
+ confirm action on the source host when the original backend information of the VIF
+ was not available. The fix moved the unplug to happen during the resize action
+ when such information is still available. See `bug #1895220`_ for more details.
+
+ .. _`bug #1895220`: https://bugs.launchpad.net/nova/+bug/1895220