← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1541348] [NEW] Regression in routers auto scheduling logic

 

Public bug reported:

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.

** Affects: neutron
     Importance: High
     Assignee: Oleg Bondarev (obondarev)
         Status: New


** Tags: l3-ipam-dhcp liberty-backport-potential

** Summary changed:

- regression in routers auto scheduling logic
+ Regression in routers auto scheduling logic

-- 
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:
  New

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


Follow ups