Comment 12 for bug 1569918

Reviewed: https://review.openstack.org/328578
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3c865148704dbb0c2b93df72dd9787a912fa2e9d
Submitter: Jenkins
Branch: stable/liberty

commit 3c865148704dbb0c2b93df72dd9787a912fa2e9d
Author: Swaminathan Vasudevan <email address hidden>
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
    (cherry picked from commit 3a5315ef8dbc6265ad2c47eebc1e2c42722a7cb4)

    Conflicts:
     neutron/db/l3_dvr_db.py
    Change-Id: I80a299d3f99113f77d2e728c3d9e000d01dacebd