Instance can not get metadata..........
There's my topology, It's a multi nodes archi that separate nova-network into a single box
http://
=======
bringing up loopback interface lo [ OK ]
stty: \/dev\/console
udhcpc (v1.17.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
starting DHCP forEthernet interface eth0 [ OK ]
cloud-setup: checking http:\/
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 1\/30: up 10.46. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 2\/30: up 11.47. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 3\/30: up 12.49. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 4\/30: up 13.50. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 5\/30: up 14.52. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 6\/30: up 15.53. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 7\/30: up 16.55. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 8\/30: up 17.56. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 9\/30: up 18.58. request failed
=======
*nat
:PREROUTING ACCEPT [2:636]
:OUTPUT ACCEPT [8:504]
:POSTROUTING ACCEPT [8:504]
:nova-network-
:nova-network-
:nova-network-
:nova-network-
:nova-network-snat - [0:0]
:nova-postrouti
-A PREROUTING -j nova-network-
-A OUTPUT -j nova-network-OUTPUT
-A POSTROUTING -j nova-network-
-A POSTROUTING -j nova-postroutin
-A nova-network-
-A nova-network-
-A nova-network-
-A nova-network-snat -j nova-network-
-A nova-network-snat -s 192.168.2.0/24 -j SNAT --to-source 192.168.1.1
-A nova-postroutin
COMMIT
# Completed on Fri Apr 8 19:02:27 2011
# Generated by iptables-save v1.4.4 on Fri Apr 8 19:02:27 2011
*filter
:INPUT ACCEPT [18191:1530656]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [35418:2835137]
:nova-filter-top - [0:0]
:nova-network-
:nova-network-INPUT - [0:0]
:nova-network-
:nova-network-local - [0:0]
-A INPUT -j nova-network-INPUT
-A FORWARD -j nova-filter-top
-A FORWARD -j nova-network-
-A OUTPUT -j nova-filter-top
-A OUTPUT -j nova-network-OUTPUT
-A nova-filter-top -j nova-network-local
COMMIT
# Completed on Fri Apr 8 19:02:27 2011
=======
I tried everything , but still failed to get metadata
Nova-network create a bridge "br100" for flat network and add eth0 to br100.
===========ip addr show====on nova-network host==========
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet 169.254.169.254/32 scope link lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,
link/ether 00:0e:7b:d0:05:ef brd ff:ff:ff:ff:ff:ff
inet6 fe80::20e:
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,
link/ether 00:19:d2:22:70:51 brd ff:ff:ff:ff:ff:ff
4: br100: <BROADCAST,
link/ether 00:0e:7b:d0:05:ef brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 brd 192.168.2.255 scope global br100
inet 192.168.1.2/24 brd 192.168.1.255 scope global br100
inet6 fe80::7e:
valid_lft forever preferred_lft forever
=======
Could someone give me some clues about this issue? I face this problem several times.
I really want to know what's the problem over there.
In my knowing , instance try to get metadata while a instance run up through 169.254.169.254:80 .
and then send discovery from on br100 , at this moment , nova-netowork will assign a ip to instance. then try to get metadata. due to instance's gateway is nova-network's br100 , So that nova-network should route 169.254.169.254 request to nova-api server . That's the reason of iptable prerouting to $nova-api_ip:8773.
ok, I check everything . but instance still can not been ssh or ping . After check console-out-put, I saw the result as above.
Thanks you guys first. Plz correct my mistake.
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Vish Ishaya
- Solved:
- Last query:
- Last reply:
This question was reopened
- by Hugo Kou