OpenStack Compute (nova)

unable to boot instances w/ DHCP (dnsmasq 2.58)

Bug #855210 reported by Dan Prince
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Critical
Vish Ishaya
OpenStack Compute (nova) 2011.3 "diablo"

Bug Description

I'm unable to boot instances when using FlatDHCP w/ nova trunk (essex).

We recently dropped the --interface option to our dnsmasq command to try and support dnsmasq 2.58 (now in the nova-trunk PPA). I believe we need to revisit this again to see why it isn't working in all cases (maverick, libvirt, flatdhcp).

Related branches

lp://qastaging/~vishvananda/nova/fix-dhcp-ms
Thierry Carrez: Approve
Diff: 127 lines (+93/-16)
2 files modified
nova/network/linux_net.py (+24/-16)
nova/tests/test_linux_net.py (+69/-0)
lp://qastaging/~vishvananda/nova/fix-dhcp
Dan Prince (community): Approve
Soren Hansen (community): Approve
Diff: 127 lines (+93/-16)
2 files modified
nova/network/linux_net.py (+24/-16)
nova/tests/test_linux_net.py (+69/-0)
Revision history for this message
Vish Ishaya (vishvananda) wrote :

Dan, I copied the new dnsmasq into milestone-proposed. Are you saying that it isn't working with the new version of the code, because I have been able to boot just fine.

Revision history for this message
Vish Ishaya (vishvananda) wrote : Re: [Bug 855210] unable to boot instances w/ DHCP (dnsmasq 2.58)

So the issue is that without bind-interface, the dhcp addresss must be the first interface on the bridge. Nova used to ensure this by removing and readding the other interface if it exists. Not sure why this is no longer happening. But as long as 10.0.0.1 (for example) is first, it works without bind-interface

Need to find out why it is not getting moved properly. I will look for a fix.

Thierry Carrez (ttx)
Changed in nova:
assignee: nobody → Vish Ishaya (vishvananda)
importance: Undecided → Critical
milestone: none → 2011.3
status: New → In Progress
OpenStack Infra (hudson-openstack)
Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
Adam Gandelman (gandelman-a) wrote :

The fix here seems to completely overwrite the IP address reassignment that takes place in driver.plug() / LinuxBridgeInterfaceDriver.ensure_bridge(), where existing IPs assigned to the physical NIC are migrated to the newly created bridge. Please see log attached to Bug #855971 .

Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.