openstack team mailing list archive
Mailing list archive
Re: After Grizzly: wrong IPs and timeouts to 169.254.169.254
On 04/13/2013 03:07 PM, Blair Zajac wrote:
The ci-info lines show it coming up with 192.168.1.2 but it should be
with 192.168.2.2. There's a router providing DHCP on the network that
the host is on, so maybe that's where it's getting the 192.168.1.2 address?
I disabled the DHCP server on 192.168.1.0/24 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 127.0.0.1 255.0.0.0 .
ci-info: eth0 : 1 . . fa:16:3e:81:d8:33
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?