Reviewed: https://review.openstack.org/304905 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3a5315ef8dbc6265ad2c47eebc1e2c42722a7cb4 Submitter: Jenkins Branch: master
commit 3a5315ef8dbc6265ad2c47eebc1e2c42722a7cb4 Author: Swaminathan Vasudevan <[email protected]> Date: Tue Apr 12 16:06:41 2016 -0700 DVR: Fix allowed_address_pair port binding with delayed fip Today when allowed_address_pairs are configured on a dvr service port and if a floatingip is associated with the allowed_address_pair port, we inherit the dvr service port's host and the device_owner to which the port is associated. But when the floatingip is created on the allowed_address_pair port after the port is associated with a dvr service port, then we apply the right port host binding and the arp_update. This patch address the issue, by checking for the host binding when there is a new floatingip configured. If host binding is missing and if the port happens to be an allowed_address_pair port, then it checks for the associated service port and if there is a single valid and active service port, then it inherits the host binding and device owner from the dvr service port and also applies the right arp entry. If there is are more than one active ports, then it returns. Closes-Bug: #1569918 Change-Id: I80a299d3f99113f77d2e728c3d9e000d01dacebd ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1569918 Title: Allowed_address_pair fixed_ip configured with FloatingIP after getting associated with a VM port does not work with DVR routers Status in neutron: Fix Released Bug description: Allowed_address_pair fixed_ip when configured with FloatingIP after the port is associated with the VM port is not reachable from DVR router. The current code only supports adding in the proper ARP update and port host binding inheritence for the Allowed_address_pair port only if the port has a FloatingIP configured before it is associated with a VM port. When the floatingIP is added later, it fails. How to reproduce. 1. Create networks 2. Create vrrp-net. 3. Create vrrp-subnet. 4. Create a DVR router. 5. Attach the vrrp-subnet to the router. 6. Create a VM on the vrrp-subnet 7. Create a VRRP port. 8. Attach the VRRP port with the VM. 9. Now assign a FloatingIP to the VRRP port. 10. Now check the ARP table entry in the router_namespace and also the VRRP port details. The VRRP port is still unbound and so the DVR cannot handle unbound ports. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1569918/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
