Unable curl 169.254.169.254 from my VM (using neutron)

asked 2014-01-08 15:07:53 -0600

rg3 gravatar image

updated 2014-01-10 14:49:05 -0600

smaffulli gravatar image

I have a question about metadata service when I launch a VM. The openstack instalation use a neutron to network and metadata service. I can launch a VM (image cirros), ping and access via ssh to VM. But when I try, from my VM, this curl 169.254.169.254:8775 I received this answer: couldn't connect to host

Looked on the log of VM I've found this message:

2014-01-07 20:55:30,918 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [23/120s]: url error [[Errno 113] No route to host]
2014-01-07 20:55:33,919 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [26/120s]: url error [[Errno 113] No route to host]
2014-01-07 20:55:36,918 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [29/120s]: url error [[Errno 113] No route to host]
2014-01-07 20:55:41,918 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [34/120s]: url error [[Errno 113] No route to host]

Looking to the nova.conf the metadata api is enable. And the port 8775 is listening as I've confirmed using this command: netstat -nap | grep 8775 tcp 0 0 0.0.0.0:8775 0.0.0.0:* LISTEN 11874/python

Can help and explain me why this happen, I will be grateful for your help.

edit retag flag offensive close merge delete

Comments

1

As far I understand 8775 is local port , you place it in URL curl http://169.254.169.254:8775
What's going to happen if you try from VM:-
# curl http://169.254.169.254/openstack/latest
# curl http://169.254.169.254/openstack/late...
OR in case of EC2 metadata:-

#  curl http://169.254.169.254/latest/meta-data
dbaxps gravatar imagedbaxps ( 2014-04-05 14:15:15 -0600 )edit
1

One more question. Please run
# ip netns list
qrouter-cb80b040-f13f-4a67-a39e-353b1c873a0d
qdhcp-166d9651-d299-47df-a5a1-b368e87b612f
# ip netns exec qrouter-cb80b040-f13f-4a67-a39e-353b1c873a0d iptables -L -t nat | grep 169
with your value of Cloud controller's router namespace.

dbaxps gravatar imagedbaxps ( 2014-04-06 01:38:37 -0600 )edit