Network creation does not notify DHCP agent

Bug #1174293 reported by Gary Kotton on 2013-04-29
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
High
Gary Kotton

Bug Description

When a new network is created, and the scheduling for the DHCP networks is supported, then DHCP agent is not selected (this would only happen if the DHCP agent was restarted).

Gary Kotton (garyk) on 2013-04-29
tags: added: grizzly-backport-potential

Fix proposed to branch: master
Review: https://review.openstack.org/27705

Changed in quantum:
assignee: nobody → Gary Kotton (garyk)
status: New → In Progress
Gary Kotton (garyk) on 2013-04-29
Changed in quantum:
milestone: none → havana-1
importance: Undecided → High
yong sheng gong (gongysh) wrote :

hi, this is by design!

yong sheng gong (gongysh) wrote :

when port is created, we will schedule the network auto. the design provides the administrator a chance to do scheduling manually between the network is created and the port is created.

Gary Kotton (garyk) wrote :

Thanks for the clarifications. This is not a bug!

Changed in quantum:
status: In Progress → Invalid
tags: removed: grizzly-backport-potential
Thierry Carrez (ttx) on 2013-05-14
Changed in quantum:
milestone: havana-1 → none
Assaf Muller (amuller) wrote :

Since the DHCP agent isn't notified of network creation, but only of port creation, the first VM that boots on a network may fail to receive a DHCP response.

This is because of an inherent race between the VM booting and the port create notification reaching the DHCP agent (And notification processing time).

If the issue is a matter of manual scheduling - Isn't the admin capable of manually scheduling a network on a DHCP agent when it is created? If so, why not? Isn't that the better solution?

Maru Newby (maru) wrote :

Assaf: I would seem that the delay in agent scheduling would make dhcp configuration only slightly slower (because dnsmasq would have to be started instead of just SIGHUP'd). Given that, should fixing agent scheduling be a priority over ensuring that vm boot does not proceed until dhcp configuration is complete (via some kind of sync at vif plug)?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers