Submitter: Jenkins
Branch:    master

commit 251922f5de2de35fb4766da6ab3e7a195c30310c
Author: Kevin Benton <>
Date:   Thu Sep 15 14:10:20 2016 -0700

    Disable DHCP on agent port removal
    The previous logic was just ripping the interface out without
    stopping dnsmasq. This would lead to a file handle remaining to the
    interface which would cause OVS to completely freak out and assign
    the same ofport to multiple ports.
    This preserves the behavior introduced in
    I40b85033d075562c43ce4d0e68296211b3241197 but just fully disables
    DHCP rather than relying on an exception generation to cause the
    Closes-bug: #1624701
    Change-Id: Icdd9ac136eeb3707c912853b134dbb58109e6940

** 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.

  OVS port pulled from under dnsmasq

Status in neutron:
  Fix Released

Bug description:
  Change [1] has triggered an issue with the DHCP agent. This can be
  reproduced as below:

  - A subnet gets deleted
  - A dhcp port is deleted
  - A notification is sent to the agent
  - DHCP agent deletes the port from OVS without killing dnsmasq first
  - dnsmasq is holding a file handle to the interface still
  - To this many times
  - OVS goes nuts with [2], where traces 'added interface tap%% on port ##' 
happens a gazillion time pointing to the same OVS and of port.


To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to