Post-binding information about router ports is missing in results of RPC
calls made by l3 agents. sync_routers code ensures that bindings are
present, however, it does not refresh router objects before returning
them - for RPC clients ports remain unbound before the next sync and
there is no necessary address scope information present to create routes
from fip namespaces to qrouter namespaces.
Conflicts:
neutron/api/rpc/handlers/l3_rpc.py
Change-Id: Ia135f0ed7ca99887d5208fa78fe4df1ff6412c26
Closes-Bug: #1759971
(cherry picked from commit ff5e8d7d6cdc6ce3cd93aededec512e1855f6c28)
Reviewed: https:/ /review. openstack. org/559496 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=29e0c7629fd 6377539e5c15e4d f34672e0bf1691
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 29e0c7629fd6377 539e5c15e4df346 72e0bf1691
Author: Dmitrii Shcherbakov <email address hidden>
Date: Sun Apr 1 21:02:10 2018 -0400
Refresh router objects after port binding
Post-binding information about router ports is missing in results of RPC
calls made by l3 agents. sync_routers code ensures that bindings are
present, however, it does not refresh router objects before returning
them - for RPC clients ports remain unbound before the next sync and
there is no necessary address scope information present to create routes
from fip namespaces to qrouter namespaces.
Conflicts: api/rpc/ handlers/ l3_rpc. py
neutron/
Change-Id: Ia135f0ed7ca998 87d5208fa78fe4d f1ff6412c26 3cd93aededec512 e1855f6c28)
Closes-Bug: #1759971
(cherry picked from commit ff5e8d7d6cdc6ce