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 1ce070c8e2edcdd58b2c032c3223bde318ec1ee9)
Reviewed: https:/ /review. openstack. org/559494 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=e53aa131ab6 5d50457efb01dee 20332f935f15d0
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit e53aa131ab65d50 457efb01dee2033 2f935f15d0
Author: Zuul <email address hidden>
Date: Fri Apr 6 22:34:55 2018 +0000
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 58b2c032c3223bd e318ec1ee9)
Closes-Bug: #1759971
(cherry picked from commit 1ce070c8e2edcdd