I'm not sure if there's an open bug on this or not (definitely should be), but
you're attempting to perform operations using a SERVICE_TOKEN and
On Mar 22, 2012, at 1:42 PM, Joshua Harlow harlo...@yahoo-inc.com wrote:
When trying to
Accidentally hit send...
Anyway... which does not necessarily correspond to a normal user with a service
The error message should explain this and direct you to use an OS_USERNAME,
OS_PASSWORD, OS_TENANT_* and OS_AUTH_URL instead (which can have a service
So this means ec2 won't work because it can't have a service catalog?
All of those variables should of been set:
On 3/22/12 1:39 PM, Dolph
With *all* services, if you know the endpoint you can query them
directly with the auth mechanism (either token or ec2 access/secret).
OpenStack has an identity service (keystone) that returns a catalog of
services (for discovery)
You don't need to look at the catalog if you know the endpoints.
I'm still confused.
Is there a bug in the keystone client that is causing these attributes to not
I am assuming yes, since devstack.org is doing the same calls.
Which should blow up in the same place.
Thx for the
For anyone following along, this is now being tracked in
On Thu, Mar 22, 2012 at 5:21 PM, Joshua Harlow harlo...@yahoo-inc.comwrote:
I’m still confused.
Is there a bug in the keystone client that is causing these attributes to
Mail list logo