Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

does anybody know how to actually fix the problem of Ubuntu Cloud VM instances in OpenStack not being able to import public keys from Nova-api's meta-data server with the following message:

2012-07-18 11:05:45,409 -[WARNING]: '' failed [113/120s]: url error [[Errno 111] Connection refused]
2012-07-18 11:05:52,419 -[CRITICAL]: giving up on md after 120 seconds

I've found numerous mentions of the problem (e.g. here or here) and tried turning this iptables rule on/off (using iptables-save and iptables-apply), but it doesn't work. The funny rule seems to be:

$ iptables -t nat -L -v | grep -n3
49-Chain nova-network-PREROUTING (1 references)
50- pkts bytes target     prot opt in     out     source               destination         
51:   32  1920 DNAT       tcp  --  any    any     anywhere         tcp dpt:http to:
52-    0     0 DNAT       udp  --  any    any     anywhere     udp dpt:1000 to:
54-Chain nova-network-float-snat (1 references)

Is there any good way to manually debug this, by the way?

share|improve this question

1 Answer 1

up vote 1 down vote accepted

Fixing the issue on an all-in-one deployment

With the help of the good folks at the IRC channel #openstack (zynzel, livemoon) we solved this by simply restarting nova-api:

sudo restart nova-api

You can verify that the metadata server is indeed up by issuing:

lsof -i:8775

from your controller node or

nmap -sS -sV -O -P0 -p8773-8776 <controller_ip>

with your controller node's IP address and checking that port 8775/tcp is open and listened to.

It might be the case that this is a problem with Dodai-deploy, as nova-api has to be installed after nova-compute is installed for the meta-data server to be initialized correctly.

Fixing the issue on a multinode doployment

If you run a multihost deployment and want to use Ubuntu cloud instances that pull in public keys from a metadata server you need this in your controller's nova.conf:


and this in your compute node's nova.conf:


Without this you'll get errors in your instance's console output (nova console-log test-instance) about it not being able to reach the metadata server and you won't be able to ssh into them.

Another solution is to tell your instance who you are on Launchpad through the user-data Dashboard form (or file in the terminal) so that it can pull in your public keys from there. The syntax is (not explained anywhere else but in the source code):

ssh_import_id: [your-launchpad-username]
share|improve this answer
oh, and after restarting nova-api, also reboot your VM instance so that it tries to import the public key once again. – metakermit Jul 18 '12 at 15:03

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.