38286dbd2e
In case when related dvr router is configured by L3 agent, it is first added to the tasks queue and then processed as any other router hosted on the L3 agent. But if L3 agent will ask neutron server about details of such router, it wasn't returned back as this router wasn't really scheduled to the compute node which was asking for it. It was "only" related to some other router scheduled to this compute node. Because of that router's info wasn't found in reply from the neutron-server and L3 agent was removing it from the compute node. Now _get_router_ids_for_agent method from the l3_dvrscheduler_db module will check router serviceable ports for each dvr router hosted on the compute node and will then find all routers related to it. Thanks to that it will return routers which are on the compute node only because of other related routers scheduled to this host and such router will not be deleted anymore. Change-Id: I689d5135b7194475c846731d846ccf6b25b80b4a Closes-Bug: #1884527 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_l3_dvr_ha_router_plugin.py | ||
| test_l3_dvr_router_plugin.py | ||