Bug 2015531

Summary: Nova evacuate fails due to timeout waiting for a network-vif-plugged event for instance
Product: Red Hat OpenStack Reporter: Takashi Kajinami <tkajinam>
Component: openstack-neutronAssignee: Slawek Kaplonski <skaplons>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: alifshit, averdagu, bcafarel, bdobreli, chrisw, dasmith, eglynn, froyo, jhakimra, kchamart, knoha, mlavalle, ralonsoh, sbauza, scohen, sgordon, skaplons, smooney, vromanso
Target Milestone: z9Keywords: Reopened, Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-15.2.1-1.20220805143813.40d217c.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2135922 (view as bug list) Environment:
Last Closed: 2022-12-07 20:28:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2135922    

Description Takashi Kajinami 2021-10-19 12:54:00 UTC 
Description of problem:

A customer is now validating the fix of bug 1917675 .
They initially tested evacuated without any additional configuration, but the evacuate failed with the same error (Timeout waiting for the network-vif-plugged event)

After checking the change introduced in neutron[1], we learned the following configuration should be added to neutron.conf.
~~~
[nova]
live_migration_events=True
~~~

[1] https://review.opendev.org/c/openstack/neutron/+/766277


The parameter was added to neutron.conf in all nodes and all neutron services were restarted.

However even after the parameter is applied we still observe the same timeout error.
Looking at neutron-server.log there is no network-vif-plugged sent from neutron to nova
even when the port was bound to the destination compute node.


Version-Release number of selected component (if applicable):
RHOSP16.1.6

How reproducible:
Always

Steps to Reproduce:
1. Stop a compute node:
   $ openstack compute service set --disable --down compute-0 nova-compute
   $ openstack baremetal node power off compute-0
2. Evacuate an instance on the node: nova evacuate <instance-id>

Actual results:
Evacuation fails and the instance becomes ERROR status

Expected results:
Evacuation succeeds and the instance is rebuilt on the destination compute node

Additional info:
Comment 49 errata-xmlrpc 2022-12-07 20:28:59 UTC 
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 (Moderate: Red Hat OpenStack Platform 16.1.9 (openstack-neutron) security update), 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/RHSA-2022:8870