Greetings: It seems that I am unable to authenticate against the current Keystone, and I am not sure if it is a bug or a local misconfiguration. So, before I file in Launchpad, I'd like someone to verify that I am doing the right thing.
The problem looks like this: [zaitcev@kvm-rei zaitcev]$ keystone --os_auth_url=http://localhost:35357/v2.0 --os_username=admin --os_password=admpass --os_tenant_name=admten user-list No handlers could be found for logger "keystoneclient.v2_0.client" Authorization Failed: An unexpected error prevented the server from fulfilling your request. incomplete format (HTTP 500) The server logs this: 2012-03-30 21:35:41 ERROR [root] incomplete format Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/keystone/common/wsgi.py", line 184, in __call__ result = method(context, **params) File "/usr/lib/python2.7/site-packages/keystone/service.py", line 292, in authenticate metadata=metadata_ref) File "/usr/lib/python2.7/site-packages/keystone/common/manager.py", line 48, in _wrapper return f(*args, **kw) File "/usr/lib/python2.7/site-packages/keystone/catalog/backends/sql.py", line 167, in get_catalog catalog[region][srv_type]['publicURL'] = public_url % d ValueError: incomplete format 2012-03-30 21:35:41 DEBUG [keystone.common.wsgi] ******************** RESPONSE HEADERS ******************** 2012-03-30 21:35:41 DEBUG [keystone.common.wsgi] Content-Type = application/json 2012-03-30 21:35:41 DEBUG [keystone.common.wsgi] Vary = X-Auth-Token 2012-03-30 21:35:41 DEBUG [keystone.common.wsgi] Content-Length = 161 2012-03-30 21:35:41 DEBUG [keystone.common.wsgi] 2012-03-30 21:35:41 DEBUG [keystone.common.wsgi] ******************** RESPONSE BODY ******************** 2012-03-30 21:35:41 DEBUG [keystone.common.wsgi] {"error": {"message": "An unexpected error prevented the server from fulfilling your request. incomplete format", "code": 500, "title": "Internal Server Error"}} 2012-03-30 21:35:41 DEBUG [eventlet.wsgi.server] 127.0.0.1 - - [30/Mar/2012 21:35:41] "POST /v2.0/tokens HTTP/1.1" 500 327 0.260567 Yay, a traceback. However, it may be hinting that some kind of publicURL field is not set somewhere. Does this looks familiar to anyone? BTW, authentication with token works, and produces this: [zaitcev@kvm-rei zaitcev]$ keystone --endpoint http://kvm-rei:35357/v2.0 --token=758ce883df47 user-list +----------------------------------+---------+-------+---------+ | id | enabled | email | name | +----------------------------------+---------+-------+---------+ | 5c3c279d18f541aa859178869584ca40 | True | None | zaitcev | | ed6aa912c28849c0913cb1106bb26b8c | True | None | admin | +----------------------------------+---------+-------+---------+ So, the Keystone server kinda-sorta works, just not really. -- Pete _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp