yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2071721@xxxxxxxxxxxxxxxxxx>]

Hello Max:

This behaviour is reported in [1]. This limitation was implemented in
[2] and documented in [3].

In your case in particular, what you are doing is assigning an IP
address that is in use; that is not possible. You should assign as an
allowed address an VIP, that means an IP address reserved only for this.
You can create a port to reserve this VIP and this port will be
considered as type=virtual. What you are trying is not possible in
ML2/OVN.

Regards.

[1]https://bugs.launchpad.net/neutron/+bug/2018529
[2]https://review.opendev.org/c/openstack/neutron/+/882588
[3]https://docs.openstack.org/releasenotes/neutron/2023.2.html


** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2071721

Title:
  [OVN] unshelve not working when referenced by allowed address

Status in neutron:
  Invalid

Bug description:
  Reproducer:
  1. create 2 VMs
  2. openstack port set --allowed-address ip-address=<IP of VM1> <VM 2 Port ID>
  3. openstack server shelve <VM 1>
  4. openstack server unshelve <VM 1>

  unshelve triggers "nova.exception.VirtualInterfaceCreateException:
  Virtual Interface creation failed" on the selected nova-compute

  This happens because northd changes the VM port 1 to type: virtual between step 3 and 4.
  Ports with type virtual will not be plugged by the ovn-controller.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2071721/+subscriptions