Open Stack

On 08/09/2012 06:45 AM, Jay Pipes wrote:
> What was excruciating about the subscription process?

There's many more steps to subscribing to a Launchpad mailing list than 
good ol' mailman and the like. I'm just whinging off topic. Sorry... 
Thanks for your reply though!

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

It's all on one box. So the same one I suppose.

>
>> But doing something like:
>>
>> I get a HTTP 500 error.
>
> I think you're missing a paste above :) doing something like what?
>

My bad. Something like:
curl http://169.254.169.254:8775/1.0/
or
curl http://169.254.169.254:8775/2009-04-04/
or
curl http://169.254.169.254:8775/2009-04-04/meta-data/instance-id

Also I notice that the error message above does not contain the port. Is 
that normal, or is it really not accessing the correct port?

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

I guess I'll have to build a VM from scratch, as I was relying on the 
ssh key to be able to ssh into the VM, which apparently is supplied by 
the meta-data service.

If that is the case, I can use it without the meta-data service, though 
it sure would be nice to have it working properly eventually.

Cheers,

Simon


-- 
simonsmicrophone.com