Update nova network info when doing rebuild for evacuate operation
When nova evacuate or host-evacuate are used to recreate instances with
sriov ports the instances are allocated new device ids on the target and
neutron is updated accordingly. However the network info data passed
to the driver spawn method is not updated and thus the instance tries
to use the device id they were allocated on the source node. If a pre
existing instance is using that device id or no such device exists on
the target node then the instance will fail to start.
Reviewed: https:/ /review. openstack. org/605882 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=9e146072b6a b5c614cc4502170 cc686cc8cc7bce
Committed: https:/
Submitter: Zuul
Branch: stable/ocata
commit 9e146072b6ab5c6 14cc4502170cc68 6cc8cc7bce
Author: paul-carlton2 <email address hidden>
Date: Thu Oct 6 12:02:15 2016 +0100
Update nova network info when doing rebuild for evacuate operation
When nova evacuate or host-evacuate are used to recreate instances with
sriov ports the instances are allocated new device ids on the target and
neutron is updated accordingly. However the network info data passed
to the driver spawn method is not updated and thus the instance tries
to use the device id they were allocated on the source node. If a pre
existing instance is using that device id or no such device exists on
the target node then the instance will fail to start.
Conflicts:
nova/ compute/ manager. py
nova/ tests/unit/ compute/ test_compute_ mgr.py
NOTE(mriedem): The conflict is due to not having change 4995df22b656bb2 e9bddaec6d775cc in Ocata.
Iddae807455
Co-Authored-By: Steven Webster <email address hidden> bd4ea5bceecda81 05b6fee93dc 8da9d8b5f9a0ee8 89d9c1c6be) f9dca21edfaa754 a2848013c3) 7183888133bef68 fe28c62c7a)
Change-Id: I860ab9cf3f9a38
Closes-Bug: #1630698
Related-Bug: #1677621
(cherry picked from commit 8e052c7fe9262c3
(cherry picked from commit 559de0d0a3df92e
(cherry picked from commit c5d8594cb62c139