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 => kilo-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/1429737

Title:
  Do not notify dead DHCP agent about removed network

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

Bug description:
  In cases when networks are removed from the dead DHCP agent in the process of autorescheduling, notifying dead agent leaves messages on its queue.
  If that agent is started again, these messages would be the first it will process. 
  If there are a dozen of such messages, their processing may overlap with processing of active networks, so potentially DHCP agent may disable dhcp for active networks that it hosts.

  An example of such problem could be a system with one DHCP agent where
  it is stopped, networks removed and then it is started again. The more
  networks the agent hosts the more chances that processing of some
  network.delete.end notification would appear after dhcp is enabled on
  that network.

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