yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

** Changed in: neutron
    Milestone: None => juno-3

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1230323

Title:
  Race condition with multiple neutron-servers can allow a router to be
  scheduled twice

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  In an environment with multiple neutron-servers, I have observed that
  a router can get scheduled to an l3-agent more than once.  A "neutron
  l3-agent-list-hosting-router <router id>"  will show the router
  scheduled twice to the same l3-agent or perhaps to two different
  agents.  This can be reproduced using devstack.  A second neutron-
  server on another host has to be configured.  Executing a script
  against each of the neutron-servers which adds (neutron l3-agent-
  router-add)  and removes (neutron l3-agent-router-remove) a router
  from an l3 agent is the quickest way to reproduce the race condition.
  There is no locking or other coordination across multiple neutron-
  server processes to prevent this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1230323/+subscriptions