Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Instance metadata not found (http error [404]) for instances started on a compute node

I installed OpenStack Diablo release on two nodes: a controller node with (api, compute, network, scheduler, vncproxy) and a compute node with (compute, network). I use FlatDHCPManager.

The problem is that instances started on the compute node can not find meta data (they can reach the api server) I can ping those instances but not ssh. The console output contains the following error: ... cloud-init start-local running: Mon, 27 Feb 2012 19:48:47 +0000. up 1.95 seconds no instance data found in start-local cloud-init-nonet waiting 120 seconds for a network device. ci-info: lo : 1 127.0.0.1 255.0.0.0
ci-info: eth0 : 1 192.168.22.40 255.255.255.0 02:16:3e:70:79:48 ci-info: route-0: 0.0.0.0 192.168.22.20 0.0.0.0 eth0 UG ci-info: route-1: 192.168.22.0 0.0.0.0 255.255.255.0 eth0 U cloud-init start running: Mon, 27 Feb 2012 19:48:59 +0000. up 14.12 seconds 2012-02-27 19:49:09,381 - DataSourceEc2.py[WARNING]: 'http://169.254.169.254' failed: http error [404] 2012-02-27 19:49:10,487 - DataSourceEc2.py[WARNING]: 'http://169.254.169.254' failed: http error [404] 2012-02-27 19:49:11,591 - DataSourceEc2.py[WARNING]: 'http://169.254.169.254' failed: http error [404] ...

instances on the controller node run correctly. I also use the flag --ec2_dmz_host on the compute node