yahoo-eng-team team mailing list archive

[Kevin Benton <1625867@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The DHCP agent ends up asking for IPs on subnets it already has IPs on
because of the following  order of events:


neutron_port_create (for DHCP port)
neutron_port_status_update (from l2 agent for dhcp port)
neutron_subnet_create

However, because the dhcp agent uses a semaphore, events may be
processed in this order

subnet_create_end (which DHCP agent uses to update dhcp port)
port_update_end (which has the DHCP agent's port from port_status_update and causes the agent to think IPs have changed and retriggers a request to the server)

The issue here is that the agent is recognizing the port update message
as stale.

** Affects: neutron
     Importance: Undecided
     Assignee: Kevin Benton (kevinbenton)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => Kevin Benton (kevinbenton)

** Changed in: neutron
    Milestone: None => newton-rc2

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

Title:
  dhcp agent not discarding stale updates

Status in neutron:
  In Progress

Bug description:
  The DHCP agent ends up asking for IPs on subnets it already has IPs on
  because of the following  order of events:

  
  neutron_port_create (for DHCP port)
  neutron_port_status_update (from l2 agent for dhcp port)
  neutron_subnet_create

  However, because the dhcp agent uses a semaphore, events may be
  processed in this order

  subnet_create_end (which DHCP agent uses to update dhcp port)
  port_update_end (which has the DHCP agent's port from port_status_update and causes the agent to think IPs have changed and retriggers a request to the server)

  The issue here is that the agent is recognizing the port update
  message as stale.

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