Cannot log into instance when network_manager=FlatManager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
If I set network_manager to FlatManager, I can start a new instance, but cannot log into it.
The result of the euca-run-instances is something like the followings:
{{{
RESERVATION r-sw4pptr7 IRT
INSTANCE i-00000001 ami-qzt0fqao 10.0.0.2 10.0.0.2 running mykey (IRT, ubuntu7) 0 m1.tiny 2011-01-14 08:06:22 nova
}}}
And nova.conf is as followings:
ubuntu7 = 192.168.32.202
{{{
--sql_connectio
--s3_host=ubuntu7
--rabbit_
--cc_host=
--ec2_url=http://
--daemonize=1
--dhcpbridge_
--dhcpbridge=
--FAKE_
--ca_path=
--keys_
--networks_
--instances_
--images_
--buckets_
--libvirt_type=kvm
--network_
--vlan_
--logdir=
--verbose
--volume_
--fixed_
--network_size=64
}}}
The last part of euca-get-
{{{
Jan 14 08:08:30 ttylinux_host authpriv.info dropbear[267]: Running in background
############ debug end ##############
cloud-setup: failed to read iid from metadata. tried 30
stty: \/dev\/console
sshd is already running.
stty: \/dev\/console
startup inetd [ OK ]
stty: \/dev\/console
startup crond [ OK ]
wget: can't connect to remote host (169.254.169.254): No route to host
cloud-userdata: failed to read instance id
===== cloud-final: system completely up in 127.97 seconds ====
wget: can't connect to remote host (169.254.169.254): No route to host
wget: can't connect to remote host (169.254.169.254): No route to host
wget: can't connect to remote host (169.254.169.254): No route to host
instance-id:
public-ipv4:
local-ipv4 :
=> First-Boot Sequence:
setting shared object cache [running ldconfig] [ OK ]
}}}
And /etc/network/
{{{
auto lo
iface lo inet loopback
auto br100
iface br100 inet dhcp
bridge_fd 0
}}}
Does anybody has some ideas about this problem?
That console output looks like what happens when an EC2 image is used on OpenStack, it is trying to get it's metadata. Is this an image you created or did it come from somewhere else? Images for EC2 use will require some modification to run properly.