nova evacuate does not update instance's neutron port location in the DB

[Daniel Gauthier]

nova evacuate and nova host-evacuate doesn't update the database with the new neutron port location after the instance has successfully evacuate.

The instance's neutron port is created on the right compute node and the neutron port is created correctly using openvswitch. The instance doesn't lose connectivity.

Everything is fine with migrate/live-migration/host-live-migration

To reproduce:
shutdown a compute node and execute a nova evacuate or a nova host-evacuate.

Expected Result:
neutron port-show <port_id> show the neutron port are updated with the new neutron port location

Actual Result:
neutron port-show <port_id> still show the previous compute node

Version used :
ii nova-api 1:2015.1.0-0ubuntu1.1~cloud0 all OpenStack Compute - API frontend
ii nova-cert 1:2015.1.0-0ubuntu1.1~cloud0 all OpenStack Compute - certificate management
ii nova-common 1:2015.1.0-0ubuntu1.1~cloud0 all OpenStack Compute - common files
ii nova-conductor 1:2015.1.0-0ubuntu1.1~cloud0 all OpenStack Compute - conductor service
ii nova-novncproxy 1:2015.1.0-0ubuntu1.1~cloud0 all OpenStack Compute - NoVNC proxy
ii nova-scheduler 1:2015.1.0-0ubuntu1.1~cloud0 all OpenStack Compute - virtual machine scheduler
ii python-nova 1:2015.1.0-0ubuntu1.1~cloud0 all OpenStack Compute Python libraries
ii python-novaclient 1:2.22.0-0ubuntu1~cloud0 all client library for OpenStack Compute API

[Mark Doffman (mjdoffma)]

I believe that these bugs have been fixed by https://review.openstack.org/#/c/213461/.

Take a look at https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2789 to see where port mappings are updated.

Could you try this on the latest nova version and see if you are still having the same issue?

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]