Description of problem: Live migration time out when using live_migration_wait_for_vif_plug=true with OVN along the patch from 1563110 [1] When attempting to migrate using the new packages and with the live_migration_wait_for_vif_plug=True option, the migration command will block for 300 seconds and then return. Examining the host that the instance is running on shows that it did not move to the new host after the migration command returns. When it comes to "Timing Out," I'm referring to this type of message in the nova-compute log file on the compute node that the instance is running on (cmp001): 2018-10-23 13:07:19.941 1 WARNING nova.compute.manager [req-282046eb-ab20-4bc4-86b1-d5f8eab357b4 2f1ac6c934674865aeaabf559194e7e6 e736a09c8e77448cafc1586d060a496d - default default] [instance: 0348af86-a5cd-4bd4-b525-2650ebdfbfdf] Timed out waiting for events: [('network-vif-plugged', u'78e80031-7cda-44b2-9748-2d4ba1c8f61b')]: Timeout: 300 seconds [1] https://bugzilla.redhat.com/show_bug.cgi?id=1563110 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verified on puddle 13.0-RHEL-7/2019-10-18.1 (z9_plus_2.11) with python-networking-ovn-4.0.3-13.el7ost.noarch Before the test I set in /var/lib/config-data/puppet-generated/nova/etc/nova/nova.conf live_migration_wait_for_vif_plug=true and restarted nova services containers. Verified that live migration works by running command as follows: time openstack server migrate 9c3330f7-d2ba-4dbe-8255-eec3f48985c0 --live compute-1.redhat.local --block-migration --wait Verified that network-vif-plugged events were logged in nova and neutron logs.
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3803