<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Helvetica, Arial, sans-serif">I installed a minimal
cloud image (cirros) and found that it had no network configures
after booting. Even running udhcpc manually does not work - it
never gets an answer from dhcp.<br>
<br>
I checked and dnsmasq is running on all of the the compute nodes:<br>
/usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file=
--domain=novalocal
--pid-file=/var/lib/nova/networks/nova-br100.pid
--listen-address=10.10.11.135 --except-interface=lo
--dhcp-range=10.10.11.130,static,120s --dhcp-lease-max=64
--dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf
--dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro<br>
<br>
Why would the DHCP not be working? I am running out of ideas
here. Have tried everything I can read from searching google and
still multi_host does not come close to working. I am now even
considering abandoning OpenStack and going back to Eucalyptus. I
have even tried changing to FlatNetwork with flat_injected=True
and then IPs are set in the VMs but the metadata service still
fails (no route to host).<br>
<br>
I have checked and each host has the 169.254.269.254 addresses
natted to itself.<br>
</font><font face="Helvetica, Arial, sans-serif">I have also deleted
and recreated the network with the --multi_host=T flag.<br>
<br>
</font><font face="Helvetica, Arial, sans-serif">I have this on the
"controller":<br>
#--routing_source_ip=10.10.20.114<br>
--ec2_dmz_host=10.10.20.114<br>
--multi_host=True<br>
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata<br>
--dmz_cidr=10.10.20.114/32<br>
<br>
And this on the compute nodes:<br>
#--routing_source_ip=10.10.20.114<br>
--ec2_dmz_host=10.10.20.114<br>
--multi_host=True<br>
--enabled_apis=metadata<br>
--dmz_cidr=10.10.20.114/32<br>
<br>
<br>
</font>
<div class="moz-cite-prefix">On 03/07/2012 10:03, Marnus van Niekerk
wrote:<br>
</div>
<blockquote cite="mid:4FF2A760.4050107@mjvn.net" type="cite">On
03/07/2012 09:53, Marnus van Niekerk wrote:
<br>
<blockquote type="cite">I can now see the bridge created and
assigned an address on each compute node, but all of the VMs get
stuck after the bootloader - they never boot any further.
<br>
</blockquote>
<br>
Sorry, they do actually boot after a while but without any
networking..
<br>
<br>
cloud-init-nonet waiting 120 seconds for a network device.
<br>
cloud-init-nonet gave up waiting for a network device.
<br>
ci-info: lo : 1 127.0.0.1 255.0.0.0 .
<br>
ci-info: eth0 : 1 . .
fa:16:3e:39:5f:02
<br>
route_info failed
<br>
Waiting for network configuration...
<br>
Waiting up to 60 more seconds for network configuration...
<br>
Booting system without full network configuration...
<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
</body>
</html>