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
Given the stack trace for doing something that was seemingly normal, I've
raised a bug report on it.
https://bugs.launchpad.net/keystone/+bug/958135
Kev
On 17 March 2012 18:33, Kevin Jackson ke...@linuxservices.co.uk wrote:
Ah, one more thing - noticed this in keystone (there is an error
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:
Weird entry in the internalurl list for my EC2 endpoint - its listing
the endpoint for Nova instead (I'll raise a bug on that - looks like a copy
and paste in code typo) but only thing that looks odd to me.
Updated keystone endpoint-list table (there human err creating the
endpoints so no bug)...
On Fri, Mar 16, 2012 at 11:01 AM, Kevin Jackson
ke...@linuxservices.co.uk wrote:
[...]
NOVA_REGION=nova
export NOVA_USERNAME=demo
export NOVA_PROJECT_ID=demo
export NOVA_PASSWORD=openstack
export NOVA_API_KEY=openstack
export NOVA_REGION_NAME=$NOVA_REGION
export
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
6 matches
Mail list logo
