commit 48ea7da6c52ee14f0e9cc244fbc834283a8e74a7
Author: Miguel Lavalle <email address hidden>
Date: Sat Oct 26 18:43:56 2019 -0500
Router synch shouldn't return unrelated routers
[0] introduced the concept of connected routers: routers that are
connected to the same subnets. When a L3 agent is synching a router
with connected routers, the data of the entire set should be returned
to the agent by the Neutron server.
However, if an agent tries to synch a router with
no connected routers when the same agent has other routers that are
connected among them, the Neutron server returns the former and the
latter. For details of how this bug can manifest itself, please see [1].
This change prevents this situation: only the synched router is
returned.
Reviewed: https:/ /review. opendev. org/691498 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=48ea7da6c52 ee14f0e9cc244fb c834283a8e74a7
Committed: https:/
Submitter: Zuul
Branch: master
commit 48ea7da6c52ee14 f0e9cc244fbc834 283a8e74a7
Author: Miguel Lavalle <email address hidden>
Date: Sat Oct 26 18:43:56 2019 -0500
Router synch shouldn't return unrelated routers
[0] introduced the concept of connected routers: routers that are
connected to the same subnets. When a L3 agent is synching a router
with connected routers, the data of the entire set should be returned
to the agent by the Neutron server.
However, if an agent tries to synch a router with
no connected routers when the same agent has other routers that are
connected among them, the Neutron server returns the former and the
latter. For details of how this bug can manifest itself, please see [1].
This change prevents this situation: only the synched router is
returned.
[0] https:/ /review. opendev. org/#/c/ 597567 /bugs.launchpad .net/neutron/ +bug/1838449/ comments/ 15
[1] https:/
Change-Id: Ibbf35d0f4a0bf9 281f0bc8c411e85 27eed75361d
Closes-Bug: #1838449