neutron/releasenotes/notes/ovn-virtual-port-prevent-binding-50efba5521e8a28e.yaml
Rodolfo Alonso Hernandez a3b00768d6 Check the device ID and host ID during virtual port binding
If a port receives a device ID and a binding profile host ID
fields update, at the same time, this is because Nova is trying
to bind the port to a VM (device ID) in a host (host ID). In
ML2/OVN, a virtual port cannot be bound to a VM.

NOTE:
* A virtual port can receive a host ID update. That happens when
  the fixed IP port that has the virtual port IP address as
  allowed address pair is bound.
* A virtual port can receive a devide ID update. Octavia uses
  the devide ID to identify to what load balancer the virtual
  port belongs.

This check was introduced in [1].

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

Closes-Bug: #2028651
Related-Bug: #2018529
Change-Id: I8784c6716f5a53b91d43323771e6f30fa8e8e506
2023-08-28 09:50:10 +00:00

11 lines
554 B
YAML

---
other:
- |
A ML2/OVN virtual port cannot be bound to a virtual machine. If a port
IP address is assigned as an allowed address pair into another port, the
first one is considered a virtual port. If the second port (non-virtual)
is bound to ML2/OVN, the virtual port cannot be bound to a virtual
machine; a virtual port is created only to reserve a set of IP addresses
to be used by other ports. The OVN mechanism driver prevents that a virtual
port has a device ID; a device ID is provided when the port is being bound.