411c45842f
This reverts commit 8e6d5d404c.
As detailed in the bug, this is overly racy, waiting for the event
potentially a long ways (and a couple RPC calls) away from where
the event will be triggered. The compute manager now has a generic
mechanism to do this which conflicts and replaces this functionality,
if enabled (default is off in Rocky, to be defaulted to on in Stein).
Conflicts:
nova/tests/unit/virt/libvirt/test_driver.py
nova/virt/libvirt/driver.py
Change-Id: Ibf2b5eeafd962e93ae4ab6290015d58c33024132
Closes-Bug: #1786346
11 lines
689 B
YAML
11 lines
689 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Note that the original fix for `bug 1414559`_ committed early in rocky was automatic and always
|
|
enabled. Because of `bug 1786346`_ that fix has since been reverted and superseded by an opt-in
|
|
mechanism which must be enabled. Setting ``[compute]/live_migration_wait_for_vif_plug=True``
|
|
will restore the behavior of `waiting for neutron events`_ during the live migration process.
|
|
|
|
.. _bug 1414559: https://bugs.launchpad.net/neutron/+bug/1414559
|
|
.. _bug 1786346: https://bugs.launchpad.net/nova/+bug/1786346
|
|
.. _waiting for neutron events: https://docs.openstack.org/nova/latest/configuration/config.html#compute.live_migration_wait_for_vif_plug |