Ask Your Question
0

Instance on the pure compute node cannot reach the meta data server

asked 2011-04-20 00:24:31 -0600

hyunsun-moon gravatar image

I deployed nova to the two servers, one runs api, network, scheduler, objectstore, and the other runs compute only. Instance has been proceed to the running state successfully, however, console output shows that the instance failed to start up unable to reach metadata server. See the console output below.


1 [ 0.000000] Initializing cgroup subsys cpuset^M 2 [ 0.000000] Initializing cgroup subsys cpu^M 3 [ 0.000000] Linux version 2.6.32-28-server (buildd@allspice) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #55-Ubuntu SMP Mon Jan 10 23: 57:16 UTC 2011 (Ubuntu 2.6.32-28.55-server 2.6.32.27+drm33.12)^M 4 [ 0.000000] Command line: root=/dev/vda console=ttyS0^M 5 [ 0.000000] KERNEL supported cpus:^M 6 [ 0.000000] Intel GenuineIntel^M 7 [ 0.000000] AMD AuthenticAMD^M 8 [ 0.000000] Centaur CentaurHauls^M 9 [ 0.000000] BIOS-provided physical RAM map:^M 10 [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)^M 11 [ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)^M 12 [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)^M 13 [ 0.000000] BIOS-e820: 0000000000100000 - 000000001fffb000 (usable)^M 14 [ 0.000000] BIOS-e820: 000000001fffb000 - 0000000020000000 (reserved)^M 15 [ 0.000000] BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)^M 16 [ 0.000000] DMI 2.4 present.^M 17 [ 0.000000] last_pfn = 0x1fffb max_arch_pfn = 0x400000000^M 18 [ 0.000000] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106^M 19 [ 0.000000] Scanning 1 areas for low memory corruption^M 20 [ 0.000000] modified physical RAM map:^M 21 [ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable)^M 22 [ 0.000000] modified: 0000000000001000 - 0000000000006000 (reserved)^M 23 [ 0.000000] modified: 0000000000006000 - 000000000009f000 (usable)^M 24 [ 0.000000] modified: 000000000009f000 - 00000000000a0000 (reserved)^M 25 [ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)^M 26 [ 0.000000] modified: 0000000000100000 - 000000001fffb000 (usable)^M 27 [ 0.000000] modified: 000000001fffb000 - 0000000020000000 (reserved)^M 28 [ 0.000000] modified: 00000000fffc0000 - 0000000100000000 (reserved)^M 29 [ 0.000000] init_memory_mapping: 0000000000000000-000000001fffb000^M 30 [ 0.000000] NX (Execute Disable) protection: active^M 31 [ 0.000000] ACPI: RSDP 00000000000f8940 00014 (v00 BOCHS )^M 32 [ 0.000000] ACPI: RSDT 000000001fffde30 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)^M 33 [ 0.000000] ACPI: FACP 000000001ffffe70 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)^M 34 [ 0.000000] ACPI: DSDT 000000001fffdfd0 01E22 (v01 BXPC BXDSDT 00000001 INTL 20090123)^M 35 [ 0.000000] ACPI: FACS 000000001ffffe00 00040^M 36 [ 0.000000] ACPI: SSDT 000000001fffdf90 00037 (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001)^M 37 [ 0.000000] ACPI: APIC 000000001fffdeb0 00072 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001)^M 38 [ 0.000000] ACPI: HPET 000000001fffde70 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001)^M 39 [ 0.000000] No NUMA configuration found^M 40 [ 0.000000] Faking a node at 0000000000000000-000000001fffb000^M 41 [ 0.000000] Bootmem setup node 0 0000000000000000-000000001fffb000^M 42 [ 0.000000] NODE_DATA [0000000000009000 - 000000000000dfff]^M

43 [ 0.000000] bootmap [000000000000e000 - 0000000000011fff] pages 4^M 44 [ 0.000000] (6 early reservations) ==> bootmem [0000000000 - 001fffb000]^M 45 [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]^M 46 [ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000 ...

(more)
edit retag flag offensive close merge delete

7 answers

Sort by ยป oldest newest most voted
0

answered 2011-04-20 00:25:29 -0600

hyunsun-moon gravatar image

I was using VLAN mode and did iptables -t nat -A PREROUTING for the 169.254.169.254 to the API node.

edit flag offensive delete link more
0

answered 2011-04-20 00:29:53 -0600

hyunsun-moon gravatar image

Here's iptables-save result of the compute node.

Generated by iptables-save v1.4.4 on Tue Apr 19 20:27:13 2011

*nat :PREROUTING ACCEPT [229:43562] :POSTROUTING ACCEPT [10:622] :OUTPUT ACCEPT [11:693] :nova-compute-OUTPUT - [0:0] :nova-compute-POSTROUTING - [0:0] :nova-compute-PREROUTING - [0:0] :nova-compute-floating-snat - [0:0] :nova-compute-snat - [0:0] :nova-postrouting-bottom - [0:0] -A PREROUTING -j nova-compute-PREROUTING -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 121.166.195.54:8773 -A POSTROUTING -j nova-compute-POSTROUTING -A POSTROUTING -j nova-postrouting-bottom -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p tcp -j MASQUERADE --to-ports 1024-65535 -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p udp -j MASQUERADE --to-ports 1024-65535 -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j MASQUERADE -A OUTPUT -j nova-compute-OUTPUT -A nova-compute-snat -j nova-compute-floating-snat -A nova-postrouting-bottom -j nova-compute-snat COMMIT

Completed on Tue Apr 19 20:27:13 2011

Generated by iptables-save v1.4.4 on Tue Apr 19 20:27:13 2011

*filter :INPUT ACCEPT [475311:42792648] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [928238:74704384] :nova-compute-FORWARD - [0:0] :nova-compute-INPUT - [0:0] :nova-compute-OUTPUT - [0:0] :nova-compute-inst-18 - [0:0] :nova-compute-local - [0:0] :nova-compute-sg-fallback - [0:0] :nova-filter-top - [0:0] -A INPUT -j nova-compute-INPUT -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT -A FORWARD -j nova-filter-top -A FORWARD -j nova-compute-FORWARD -A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT -A FORWARD -i virbr0 -o virbr0 -j ACCEPT -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable -A OUTPUT -j nova-filter-top -A OUTPUT -j nova-compute-OUTPUT -A nova-compute-FORWARD -i br100 -j ACCEPT -A nova-compute-FORWARD -o br100 -j ACCEPT -A nova-compute-inst-18 -m state --state INVALID -j DROP -A nova-compute-inst-18 -m state --state RELATED,ESTABLISHED -j ACCEPT -A nova-compute-inst-18 -s 10.0.0.1/32 -p udp -m udp --sport 67 --dport 68 -j ACCEPT -A nova-compute-inst-18 -s 10.0.0.0/26 -j ACCEPT -A nova-compute-inst-18 -j nova-compute-sg-fallback -A nova-compute-local -d 10.0.0.3/32 -j nova-compute-inst-18 -A nova-compute-sg-fallback -j DROP -A nova-filter-top -j nova-compute-local COMMIT

Completed on Tue Apr 19 20:27:13 2011

edit flag offensive delete link more
0

answered 2011-04-20 00:43:48 -0600

hyunsun-moon gravatar image

It's odd because compute node can get the meta data.

GET http://169.254.169.254/

1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01 2009-04-04


I wonder, how instance can get the IP address from DHCP server on network node, with the private IP like 10.0.0.1?

edit flag offensive delete link more
0

answered 2011-04-20 01:58:31 -0600

tonytkdk gravatar image

Vlan mode , Instance should get IP from DHCP .

nova-network will bind 10.0.0.1 on nova-network host .....

edit flag offensive delete link more
0

answered 2011-04-20 07:06:48 -0600

hyunsun-moon gravatar image

I found that DHCPDISCOVERY of VM is passed to br100, but failed to be forwarded to eth0 and further network hosts in LAN. FlatDHCP has the same problem.

edit flag offensive delete link more
0

answered 2011-04-22 05:52:17 -0600

hyunsun-moon gravatar image

Hi, this was not a bug but missing a flag, --flat_interface=eth0. Thanks!

edit flag offensive delete link more
0

answered 2011-04-22 06:01:49 -0600

hyunsun-moon gravatar image

Solved.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2011-04-20 00:24:31 -0600

Seen: 89 times

Last updated: Apr 22 '11