4e78aaa694
Today Nova updates the mac_address of a direct-physical port to reflect the MAC address of the physical device the port is bound to. But this can only be done before the port is bound. However during migration Nova is not able to update the MAC when the port is bound to a different physical device on the destination host. This patch extends port binding logic for direct-physical ports to allow providing the MAC address of the physical device via the binding profile. If it is provided then Neutron overwrites the value of the mac_address field of the port with the value from the active binding profile. Also when the port is being unbound or the MAC address is removed from the active binding porfile then neutron resets the mac_address field of port to a generated MAC to avoid duplicated MAC issues when another port is being bound to the same physical device. The shim API extension for this change is being proposed in I54b4c85ffc4856fba7ad5e9e29f77f74815e1275 in neutron-lib. Depends-On: https://review.opendev.org/c/openstack/neutron-lib/+/831935 Closes-Bug: #1942329 Change-Id: Ib0638f5db69cb92daf6932890cb89e83cf84f295
15 lines
751 B
YAML
15 lines
751 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`1942329 <https://bugs.launchpad.net/neutron/+bug/1942329>`_
|
|
Port binding logic for direct-physical ports has been extended to allow
|
|
providing the MAC address of the physical device via the binding profile.
|
|
If it is provided then Neutron overwrites the value of the
|
|
``device_mac_address`` field of the port object in the database with the
|
|
value from the active binding profile.
|
|
If there are ports bound before `the nova side of this fix is depolyed
|
|
<https://review.opendev.org/c/openstack/nova/+/829248>`_ then the VM using
|
|
the port needs to be moved or the port needs to be detached and re-attached
|
|
to force nova to provide the MAC address of the direct-physical port in the
|
|
port binding.
|