Routers auto scheduling works when an l3 agent starst and performs
a full sync with neutron server. Neutron server looks for all
unscheduled routers and schedules them to that agent if applicable.
This was broken by commit 062d16ac0163f921d4255d9b77d6f903a7c5f110
which changed full sync logic a bit: now l3 agent requests all ids
of routers scheduled to it first. get_router_ids() didb't call
routers auto scheduling which caused the regression.
This patch adds routers auto scheduling to get_router_ids().
Reviewed: https:/ /review. fuel-infra. org/16645 ci/fuel- 8.0/liberty
Submitter: Pkgs Jenkins <email address hidden>
Branch: openstack-
Commit: 408d2e6f19de60d 059dc8bddadb62a 0dbbfaf4e7
Author: Oleg Bondarev <email address hidden>
Date: Wed Feb 3 10:14:03 2016
Fix regression in routers auto scheduling logic
Routers auto scheduling works when an l3 agent starst and performs 1d4255d9b77d6f9 03a7c5f110
a full sync with neutron server. Neutron server looks for all
unscheduled routers and schedules them to that agent if applicable.
This was broken by commit 062d16ac0163f92
which changed full sync logic a bit: now l3 agent requests all ids
of routers scheduled to it first. get_router_ids() didb't call
routers auto scheduling which caused the regression.
This patch adds routers auto scheduling to get_router_ids().
Closes-Bug: #1539707 93296985e169631 e5583d9fa12
Change-Id: If6d4e7b3a4839c