openstack team mailing list archive

[Kevin Jackson <kevin@xxxxxxxxxxxxxxxxxxx>]

Thanks gents,
I've updated my resource files to include the new style envvars... but I
suspect that must affect nova client only in this case.

The line is indeed present to keystone in my nova.conf.  When running euca
commands and keystone-all in a console so I see all the debug output, I
don't see any connections being made.  When running nova client, this works
a charm so the problem must be between my EC2 API service provided by
nova-api and keystone as the error is logged in nova-api.log.

I've gone through devstack configs to see if I've missed anything -
certainly doesn't appear to be the case in my nova.conf...

I'll keep working at it and compare to devstack, but any other flashes of
inspiration - send it my way!

Cheers,

Kev



On 16 March 2012 20:42, Adam Gandelman <adamg@xxxxxxxxxxxxx> wrote:

> On 03/16/2012 09:01 AM, Kevin Jackson wrote:
>
>> After successfully spinning up instances on Essex under Ubuntu 12.04 B1
>> using nova tool I'm now looking at the EC2 API / euca2ools but I'm hitting
>> an error
>>
>> $ euca-describe-instances
>> Unauthorized: Failure communicating with keystone
>>
>> /etc/nova/nova.conf:
>> --ec2_url=http://172.15.0.2:**8773/services/Cloud<http://172.15.0.2:8773/services/Cloud>
>>
>>
>
> Do you also have
> --keystone_ec2_url=http://**keystonehost:5000/v2.0/**ec2tokens<http://keystonehost:5000/v2.0/ec2tokens>
>
> ?
>
> Adam
>
>
> ______________________________**_________________
> Mailing list: https://launchpad.net/~**openstack<https://launchpad.net/%7Eopenstack>
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~**openstack<https://launchpad.net/%7Eopenstack>
> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>



-- 
Kevin Jackson
@itarchitectkev