openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #08761
euca2ools: Failure communicating with keystone (Essex on Ubuntu 12.04 B1)
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
==> /var/log/nova/nova-api.log <==
2012-03-16 15:57:08 ERROR nova.api.ec2 [-] Unauthorized: Failure
communicating with keystone
2012-03-16 15:57:08 INFO nova.api.ec2 [-] 0.123742s 172.15.0.254 POST
/services/Cloud/ None:None 400 [Boto/2.0 (linux2)]
application/x-www-form-urlencoded text/xml
environment:
NOVA_API_HOST=172.15.0.2
GLANCE_API_HOST=172.15.0.2
KEYSTONE_API_HOST=172.15.0.2
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 NOVA_URL="http://$NOVA_API_HOST:5000/v2.0/"
export NOVA_VERSION="1.1"
export OS_AUTH_USER=demo
export OS_AUTH_KEY=openstack
export OS_AUTH_TENANT=demo
export OS_AUTH_URL="http://$KEYSTONE_API_HOST:5000/v2.0/"
export OS_AUTH_STRATEGY="keystone"
export EC2_URL="http://$NOVA_API_HOST:8773/services/Cloud"
export EC2_ACCESS_KEY="026744a35b8e44788f59c2f3224a80a5"
export EC2_SECRET_KEY="e4616ab54551488f9a786b88fa31214c"
export S3_URL="http://$GLANCE_API_HOST:3333"
keystone --token 999888777666 --endpoint
http://172.15.0.2:35357/v2.0endpoint-list
+----------------------------------+--------+----------------------------------------------+----------------------------------------------+----------------------------------------------+
| id | region | publicurl
| internalurl |
publicurl |
+----------------------------------+--------+----------------------------------------------+----------------------------------------------+----------------------------------------------+
| 54df67d675f64995848a58f547fe2e0a | nova |
https://172.15.0.2:443/v1/AUTH_$(tenant_id)s |
https://172.15.0.2:443/v1/AUTH_$(tenant_id)s |
https://172.15.0.2:443/v1/AUTH_$(tenant_id)s |
| 8742d47bb7e1438d8efb56cbac29dd1d | nova |
http://172.15.0.2:8776/v1/$(tenant_id)s |
http://172.15.0.2:8776/v1/$(tenant_id)s |
http://172.15.0.2:8776/v1/$(tenant_id)s |
| 9b5cc98f8654403dbd0a8ae7b71ca3d9 | nova | http://172.15.0.2:9292/v1
| http://172.15.0.2:9292/v1 |
http://172.15.0.2:9292/v1 |
| e091a85dde53436cbfdaf90d69376e21 | nova |
http://172.15.0.2:8774/v2/$(tenant_id)s |
http://172.15.0.2:8774/v2/$(tenant_id)s |
http://172.15.0.2:8774/v2/$(tenant_id)s |
| effe286bcc2a42b7a7f6da0ebccb24ca | nova |
http://172.15.0.2:8773/services/Cloud |
http://172.15.0.2:8774/v2/$(tenant_id)s |
http://172.15.0.2:8773/services/Cloud |
| fe4faf319c6e43419efa086e4fd3f1db | nova | http://172.15.0.2:5000/v2.0
| http://172.15.0.2:5000/v2.0 |
http://172.15.0.2:5000/v2.0 |
+----------------------------------+--------+----------------------------------------------+----------------------------------------------+----------------------------------------------+
Any pointers as to what I've done wrong is appreciated.
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.
Cheers,
Kev
--
Kevin Jackson
@itarchitectkev
Follow ups