yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #47023
[Bug 1550886] [NEW] L3 Agent's fullsync is raceful with creation of HA router
Public bug reported:
When creating an HA router, after the server creates all the DB objects
(including the HA network and ports if it's the first one), the server
continues on the schedule the router to (some of) the available agents.
The race is achieved when an L3 agent router issues a sync_router
request, which later down the line ends up in an auto_schedule_routers()
call. If this happens before the above schedule (of the create_router())
is complete, the server will refuse to schedule the router to the other
intended L3 agents, resulting is less agents being scheduled.
The only way to fix this is either restarting one of the L3 agents which
didn't get scheduled, or recreating the router. Either is a bad option.
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Tags: l3-ha
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1550886
Title:
L3 Agent's fullsync is raceful with creation of HA router
Status in neutron:
In Progress
Bug description:
When creating an HA router, after the server creates all the DB
objects (including the HA network and ports if it's the first one),
the server continues on the schedule the router to (some of) the
available agents.
The race is achieved when an L3 agent router issues a sync_router
request, which later down the line ends up in an
auto_schedule_routers() call. If this happens before the above
schedule (of the create_router()) is complete, the server will refuse
to schedule the router to the other intended L3 agents, resulting is
less agents being scheduled.
The only way to fix this is either restarting one of the L3 agents
which didn't get scheduled, or recreating the router. Either is a bad
option.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1550886/+subscriptions
Follow ups