neutron

Folsom VM timed out on 169.254.169.254 after boot

Asked by arturo lorenzo

Do I need to run nova-api-metadata on every compute node? I do have three machines where one is the controller (MySQL,bbitMQ, Nova,Cinder, Glance, Keystone,Quantum), one is the network controller (Quantum-L3-agent,Quantum-DHCP-agent,Quantum Agent with OpenvSwitch) and one or more are the compute nodes (nova-compute, KVM, novaapi,Quantum Agent withOpen-vSwitch).
My problem is that I cannot get the metadata from the VMs. Get time out. Here are the last VM console messages:
=========================================================================
no instance data found in start-local
ci-info: lo : 1 127.0.0.1 255.0.0.0 .
ci-info: eth0 : 1 10.5.5.3 255.255.255.0 fa:16:3e:72:94:0a
ci-info: route-0: 0.0.0.0 10.5.5.1 0.0.0.0 eth0 UG
ci-info: route-1: 10.5.5.0 0.0.0.0 255.255.255.0 eth0 U
cloud-init start running: Thu, 24 Jan 2013 17:45:46 +0000. up 8.96 seconds
2013-01-24 17:47:16,964 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url error [timed out]
2013-01-24 17:48:08,017 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url error [timed out]
2013-01-24 17:48:26,036 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url error [timed out]
2013-01-24 17:48:27,038 - DataSourceEc2.py[CRITICAL]: giving up on md after 120 seconds
no instance data found in start
=========================================================================
Any ideas? do I need the nova-api-metadata running on the compute nodes? I can access the controller ports 8773-8776 from the compute nodes OK.
Thanks for the help!

Question information

Language:
English Edit question
Status:
Expired
For:
neutron Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Gary Kotton (garyk) said : 		#1

Please note that the blueprint (implemented in G2 - https://blueprints.launchpad.net/quantum/+spec/metadata-overlapping-networks) fixes the Quantum support for the metdata server.
You will need to run the quantum-metadata-agent on the network node (this should have connectivity to the nova meta data service and be able to be accessed via the l3 agent).
Thanks
Gary

Revision history for this message
arturo lorenzo (arturo-lorenzo) said : 		#2

Thanks Gary, I am running Quantum from Folsom using "http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/folsom main", so what do I have to do in order to add quantum-metadata-agent into that version? Any tips?
Thanks!

Revision history for this message
Tatenda Mupaso (tatenda-mupaso) said : 		#3

Arturo Lorenzo did you manage to get your metadata-proxy working by any chance? Please let me know because I was referred to this question by Gary because I was experiencing the same problem. So far I copied repositories from https://review.openstack.org/#/c/16282/ and copied/overwrote and added the new files where they were supposed to be ( I don't know if I did it right) but that's where I currently am, will let you know my progress here soon.

Revision history for this message
Launchpad Janitor (janitor) said : 		#4

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.