← Back to team overview

openstack team mailing list archive

Re: After Grizzly: wrong IPs and timeouts to


On 04/13/2013 03:29 PM, Blair Zajac wrote:
On 04/13/2013 03:07 PM, Blair Zajac wrote:
The ci-info lines show it coming up with but it should be
with  There's a router providing DHCP on the network that
the host is on, so maybe that's where it's getting the

I disabled the DHCP server on and starting another new
instance and saw this:

Begin: Running /scripts/init-bottom ... done.
[    1.156141] Refined TSC clocksource calibration: 3292.521 MHz.
[    1.532807] EXT4-fs (vda1): re-mounted. Opts: (null)
cloud-init start-local running: Sat, 13 Apr 2013 22:23:34 +0000. up 3.26
no instance data found in start-local
cloud-init-nonet waiting 120 seconds for a network device.
cloud-init-nonet gave up waiting for a network device.
ci-info: lo    : 1       .
ci-info: eth0  : 1 .               .               fa:16:3e:81:d8:33
route_info failed
Waiting for network configuration...
Waiting up to 60 more seconds for network configuration...
Booting system without full network configuration...
  * Stopping Failsafe Boot Delay   [ OK ]

So the VM is getting DHCP messages from the host network, which didn't
occur with Quantal/Folsom.  Any ideas?

After Googling I found this page [1] which had this note for 12.10 to add to /etc/rc.local:

/sbin/iptables -A POSTROUTING -t mangle -p udp --dport 68 -j CHECKSUM --checksum-fill

After doing this, re-enabling the host networks' DHCP server and rebooting the host, guests were able to correctly boot.


[1] https://wiki.ubuntu.com/SecurityTeam/TestingOpenStack#Making_OpenStack_available_to_the_LAN