EC2 + Keystone client missing attributes
This bug report was converted into a question: question #191444: EC2 + Keystone client missing attributes.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When trying to use eucarc (https:/
I am getting the following:
++ keystone catalog --service ec2
++ awk '/ publicURL / { print $4 }'
'Client' object has no attribute 'service_catalog'
+ export EC2_URL=
+ EC2_URL=
++ keystone ec2-credentials
'Client' object has no attribute 'auth_tenant_id'
+ CREDS=
++ echo ''
++ awk '/ access / { print $4 }'
+ export EC2_ACCESS_KEY=
+ EC2_ACCESS_KEY=
++ echo ''
++ awk '/ secret / { print $4 }'
+ export EC2_SECRET_KEY=
+ EC2_SECRET_KEY=
+ NOVA_KEY_DIR=
++ keystone catalog --service s3
++ awk '/ publicURL / { print $4 }'
'Client' object has no attribute 'service_catalog'
This seems to stop EC2 from being useable by euca tools and the like (since we can't register the service or get keys out)
My apologies for the confusion on the mailing list. Setting the OS_* variables should result in the following behavior:
Admin session (using SERVICE_TOKEN and SERVICE_ENDPOINT): http:// paste.openstack .org/raw/ 12051/
EC2 user session (using --os_username, etc, created above): http:// paste.openstack .org/raw/ 12050/