yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #45998
[Bug 1541348] Re: Regression in routers auto scheduling logic
Reviewed: https://review.openstack.org/275653
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=51adde5eb93993fbd24c14daab16ade74565978f
Submitter: Jenkins
Branch: master
commit 51adde5eb93993fbd24c14daab16ade74565978f
Author: Oleg Bondarev <obondarev@xxxxxxxxxxxx>
Date: Wed Feb 3 15:01:52 2016 +0300
Fix regression in routers auto scheduling logic
Routers auto scheduling works when an l3 agent starts 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 0e97feb0f30bc0ef6f4fe041cb41b7aa81042263
which changed full sync logic a bit: now l3 agent requests all ids
of routers scheduled to it first. get_router_ids() didn't call
routers auto scheduling which caused the regression.
This patch adds routers auto scheduling to get_router_ids().
Closes-Bug: #1541348
Change-Id: If6d4e7b3a4839c93296985e169631e5583d9fa12
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1541348
Title:
Regression in routers auto scheduling logic
Status in neutron:
Fix Released
Bug description:
Routers auto scheduling works when an l3 agent starst and performs a full sync with neutron server . Neutron server looks for all unscheduled routers (non-dvr routers only) and schedules them to that agent if applicable.
This was broken by commit 0e97feb0f30bc0ef6f4fe041cb41b7aa81042263 which changed full sync logic a bit: now l3 agent requests all ids of routers scheduled to it first. get_router_ids() didn't call routers auto scheduling which caused the regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1541348/+subscriptions
References