Open Stack

On 08/08/2012 03:57 AM, Simon Walter wrote:
> 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.

What was excruciating about the subscription process?

> 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]
<snip>
> 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

Where are you curl'ing from? The compute node or the host running the
nova-ec2-metadata service?

> But doing something like:
> 
> I get a HTTP 500 error.

I think you're missing a paste above :) doing something like what?

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

Well, it's unlikely it's an issue with the metadata service because the
metadata service is clearly responding properly to at least ONE host, as
evidenced above. It's more likely a routing issue.

Can you SSH into the VM in question and try pinging the EC2 metadata
service URL? (http://169.254.169.254:8775/)

Best,
-jay

> 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
>