SR-IOV port doesn't reach router internal port when they on the same physical server

[Moshe Levi]

When I used SR-IOV port instance and router port that reside on the same physical server, I can't use floating ip and access the vm.
but it is working if the SR-IOV port instance is on different physical server

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/259782

[OpenStack Infra (hudson-openstack)]

Change abandoned by Moshe Levi (<email address hidden>) on branch: master
Review: https://review.openstack.org/259782
Reason: should be resolve under the L2 agents

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/320562

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/320562
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2c8f61b816bf531a17a7b45d35a5388e8a2f607a
Submitter: Jenkins
Branch: master

commit 2c8f61b816bf531a17a7b45d35a5388e8a2f607a
Author: Edan David <email address hidden>
Date: Tue May 24 11:54:02 2016 -0400

    Adding FDB population agent extension

    The purpose of this extension is updating the FDB table upon changes of
    normal port instances thus enabling communication between direct port
    SR-IOV instances and normal port instances.
    Additionally enabling communication to direct port
    instances with floating ips.
    Support for OVS agent and linux bridge.

    DocImpact
    Change-Id: I61a8aacb1b21b2a6e452389633d7dcccf9964fea
    Closes-Bug: #1492228
    Closes-Bug: #1527991

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/neutron 9.0.0.0b2 development milestone.