Ask Your Question
0

instances can't connect whit remote host (169.254.169.254) network is unreachable

asked 2012-11-24 00:20:03 -0500

danielnuneze gravatar image

Hi everyone

I have 2 nodes ControllerNode: 172.31.15.167. It has all nova services include nova-compute ComputeNode: 172.31.15.165. It has installed only nova-api and nova-compute

I have images:

nova image-list

+--------------------------------------+-----------------------------------------------------+--------+--------+ | ID | Name | Status | Server | +--------------------------------------+-----------------------------------------------------+--------+--------+ | bfc16412-5fc1-4423-9868-92314f4066fd | Cirrus test | ACTIVE | |

I can run an instance

nova boot cirros1 --image bfc16412-5fc1-4423-9868-92314f4066fd --flavor 1 --key_name key --security_group default

nova list

+--------------------------------------+---------+--------+----------------------------------+ | ID | Name | Status | Networks | +--------------------------------------+---------+--------+----------------------------------+ | 809b9b15-c84d-4a13-8fc5-69a459a85316 | cirros1 | ACTIVE | cookbook=10.0.3.2, 172.31.15.209 | +--------------------------------------+---------+--------+----------------------------------+

The relevant output of nova console-log is

....... ....... Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40-network failed cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id (http://169.254.169.254/2009-04-04/met...) wget: can't connect to remote host (169.254.169.254): Network is unreachable cloud-setup: failed 1/30: up 11.03. request failed wget: can't connect to remote host (169.254.169.254): Network is unreachable cloud-setup: failed 2/30: up 12.05. request failed ...... ...... ############ debug start ##############

/etc/rc.d/init.d/sshd start

/etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found route: fscanf

ifconfig -a

eth0 Link encap:Ethernet HWaddr FA:16:3E:29:EF:7A
inet6 addr: fe80::f816:3eff:fe29:ef7a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1706 (1.6 KiB) TX bytes:1224 (1.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

route -n

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface route: fscanf

cat /etc/resolv.conf

cat: can't open '/etc/resolv.conf': No such file or directory

gateway not found

/etc/rc3.d/S45-cloud-setup: line 66: can't open /etc/resolv.conf: no such file ....... ....... ===== cloud-final: system completely up in 42.36 seconds ==== wget: can't connect to remote host (169.254.169.254): Network is unreachable wget: can't connect to remote host (169.254.169.254): Network is unreachable wget: can't connect to remote host (169.254.169.254): Network is unreachable instance-id: public-ipv4: local-ipv4 : wget: can't connect to remote host (169.254.169.254): Network is unreachable cloud-userdata: failed to read instance id WARN: /etc/rc3.d/S99-cloud-userdata failed

I can't ping the instance

ping 10.0.3.2

PING 10.0.3.2 (10.0.3.2) 56(84) bytes of data. From 10.0.3.1 icmp_seq=1 Destination Host Unreachable

ping 172.31.15.209

PING ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by » oldest newest most voted
0

answered 2012-11-27 04:39:51 -0500

danielnuneze gravatar image

Yes, in the first post is that line. Nova understand the instance have IPs.

nova list

+--------------------------------------+---------+--------+----------------------------------+ | ID | Name | Status | Networks | +--------------------------------------+---------+--------+----------------------------------+ | 809b9b15-c84d-4a13-8fc5-69a459a85316 | cirros1 | ACTIVE | cookbook=10.0.3.2, 172.31.15.209 | +--------------------------------------+---------+--------+----------------------------------+

but the instances can't get metadata.

===== cloud-final: system completely up in 42.36 seconds ==== wget: can't connect to remote host (169.254.169.254): Network is unreachable wget: can't connect to remote host (169.254.169.254): Network is unreachable wget: can't connect to remote host (169.254.169.254): Network is unreachable instance-id: public-ipv4: local-ipv4 : wget: can't connect to remote host (169.254.169.254): Network is unreachable cloud-userdata: failed to read instance id WARN: /etc/rc3.d/S99-cloud-userdata failed

nova.conf file needs a config line for activate some metadata service???

edit flag offensive delete link more
0

answered 2012-11-26 13:43:48 -0500

dims-v gravatar image

Check if you have an iptables rule corresponding to 169.254.169.254 http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/ (http://www.mirantis.com/blog/openstac...)

Snippet from above url - " but currently the only important rule is this one: -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 192.168.56.200:8775. It makes the nova metadata service “listen” on the link-local address 169.254.169.254 by doing DNAT from that address to its actual bind address on the controller, 192.168.56.200:8775."

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: 2012-11-24 00:20:03 -0500

Seen: 1,427 times

Last updated: Nov 27 '12