dhcp agent not discarding stale updates
Bug #1625867 reported by
Kevin Benton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Kevin Benton |
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_
neutron_
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.
Changed in neutron: | |
assignee: | nobody → Kevin Benton (kevinbenton) |
milestone: | none → newton-rc2 |
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: newton-rc-potential |
tags: | added: l3-ipam-dhcp |
tags: | removed: newton-rc-potential |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/373566
Review: https:/