← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1588906] Re: DHCP port status not active until agent restart

 

Reviewed:  https://review.openstack.org/327062
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5b0ea0320236d05bc3af0cb338e03f3c3cde040a
Submitter: Jenkins
Branch:    master

commit 5b0ea0320236d05bc3af0cb338e03f3c3cde040a
Author: Hong Hui Xiao <xiaohhui@xxxxxxxxxx>
Date:   Wed Jun 8 12:18:53 2016 +0000

    Mark port as ready after enabling dhcp at agent
    
    When subnet is created and network is scheduled to dhcp agent, the
    dhcp agent will request neutron server to create dhcp port.
    
    Neutron server will create and mark port as BUILD and wait for the
    ready signal from dhcp agent.
    
    dhcp agent will create 'real' dhcp port after getting response from
    neutron server. But after that, dhcp agent will not tell neutron server
    that the dhcp port is ready. So, the reported bug can be observed.
    
    If ports are created before dhcp is enabled for network, dhcp agent will
    not mark ports as 'ready' as there is no network cache. This patch also
    marks all ports in network as ready, in case that happens.
    
    Change-Id: I363d8727f7ef6e6e08be4b0022c6464d51692b85
    Closes-bug: #1588906


** 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.
https://bugs.launchpad.net/bugs/1588906

Title:
  DHCP port status not active until agent restart

Status in neutron:
  Fix Released

Bug description:
  Recreate Step:
  1) Deploy DevStack cloud environment with neutron ML2 OVS.
  2) Create a network and subnet with DHCP enabled.
  3) Check the DHCP port status which will be DOWN or BUILD.
  4) Restart the DHCP agent.
  5) Check the DHCP port status which will now be ACTIVE.

  I've been able to recreate this problem with ML2 OVN as well.  It
  doesn't impact OVN core plugin.  It appears that the DHCP provisioning
  block is not being completed like it once was.

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


References