← Back to team overview

openstack team mailing list archive

Help with meta-data

 


Hi all,

I've completed the excruciating Launchpad process of subscribing to a mailing list to ask for your help with having my instances access their meta-data.

I'm new to OpenStack. So please forgive my n00bness.

I installed OpenStack on Ubuntu 12.04 by following stackgeek's 10 minute method and using their scripts: http://stackgeek.com/guides/gettingstarted.html

Which got me quite far. I had to fix some of the networking setup. Now I can launch instances and ping them.

However, they cannot access their meta-data:

Begin: Running /scripts/init-bottom ... done.
cloud-init start-local running: Wed, 08 Aug 2012 07:33:07 +0000. up 8.32 seconds

no instance data found in start-local

ci-info: lo    : 1 127.0.0.1       255.0.0.0       .

ci-info: eth1  : 0 .               .               fa:16:3e:5a:f3:05

ci-info: eth0  : 1 192.168.1.205   255.255.255.0   fa:16:3e:23:d7:7c

ci-info: route-0: 0.0.0.0         192.168.1.1     0.0.0.0         eth0   UG

ci-info: route-1: 192.168.1.0     0.0.0.0         255.255.255.0   eth0   U

cloud-init start running: Wed, 08 Aug 2012 07:33:10 +0000. up 11.95 seconds

2012-08-08 07:33:54,243 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:33:57,242 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:01,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:04,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [13/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:07,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [16/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:10,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [19/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:13,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [22/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:16,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [25/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:21,250 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [30/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:24,250 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [33/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:29,254 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [38/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:35,258 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [44/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:41,261 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:47,266 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [56/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:53,269 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [62/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:59,274 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [68/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:06,278 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [75/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:13,282 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [82/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:20,285 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [89/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:27,289 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [96/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:34,294 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [103/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:42,297 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [111/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:50,302 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:55,308 - DataSourceEc2.py[CRITICAL]: giving up on md after 124 seconds



no instance data found in start

Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd


I can see something on the host:
curl http://169.254.169.254:8775/
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04

But doing something like:

I get a HTTP 500 error.

I don't know if the problem is routing or with the meta-data "service".

Any help is appreciated. I'm running this all on one box. Here is my nova.conf:
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=192.168.1.14
--ec2_host=192.168.1.14
--rabbit_host=192.168.1.14
--cc_host=192.168.1.14
--nova_url=http://192.168.1.14:8774/v1.1/
--routing_source_ip=192.168.1.14
--glance_api_servers=192.168.1.14:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.22
--sql_connection=mysql://nova:s7ack3d@127.0.0.1/nova
--ec2_url=http://192.168.1.14:8773/services/Cloud
--keystone_ec2_url=http://192.168.1.14:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--vnc_enabled=true
--vncproxy_url=http://192.168.1.14:6080
--vnc_console_proxy_url=http://192.168.1.14:6080
# network specific settings
--network_manager=nova.network.manager.FlatDHCPManager
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.0.2.0/24
--floating_range=192.168.1.30/27
--network_size=32
--flat_network_dhcp_start=10.0.2.1
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=libvirt
--root_helper=sudo nova-rootwrap
--verbose

I have a question about VNC as well, but this is by far more important.

Thanks for your help,

Simon

--
simonsmicrophone.com



Follow ups