Dashboard Error: Unable to retrieve user list.

[Marco CONSONNI]

Not sure this is a documentation/configuration problem.

It could be a Horizon problem not yet reported or - maybe - a problem with my own installation...

I successfully installed Horizon following instructions here http://docs.openstack.org/trunk/openstack-compute/install/content/ch_install-dashboard.html.

When I select Admin/Users I get the following error: "Error: Unable to retrieve user list".

I made some investigation on this.

The request is sent to apache and fails with the following traceback:

[Fri Apr 27 13:30:45 2012] [error] Request returned failure status.
[Fri Apr 27 13:30:45 2012] [error] Traceback (most recent call last):
[Fri Apr 27 13:30:45 2012] [error] File "/usr/lib/python2.7/dist-packages/keystoneclient/client.py", line 121, in request
[Fri Apr 27 13:30:45 2012] [error] body = json.loads(body)
[Fri Apr 27 13:30:45 2012] [error] File "/usr/lib/python2.7/json/__init__.py", line 326, in loads
[Fri Apr 27 13:30:45 2012] [error] return _default_decoder.decode(s)
[Fri Apr 27 13:30:45 2012] [error] File "/usr/lib/python2.7/json/decoder.py", line 369, in decode
[Fri Apr 27 13:30:45 2012] [error] raise ValueError(errmsg("Extra data", s, end, len(s)))
[Fri Apr 27 13:30:45 2012] [error] ValueError: Extra data: line 1 column 4 - line 5 column 4 (char 4 - 52)

I don't see any log at nova-api level.

[Martin Samson (pyrolian)]

I have the exact same issue. Fresh OpenStack Essex on ubuntu 12.04

[Omri Siri (omri-o)]

I had the same problem (Fresh openstack essex ubuntu 12.04), in my case it was due to a wrong configuration in /etc/keystone/default_catalog.templates

the identity server should be configured similarly to:
catalog.RegionOne.identity.publicURL = http://<%= keystone_server %>:5000/v2.0
catalog.RegionOne.identity.adminURL = http://<%= keystone_server %>:35357/v2.0
catalog.RegionOne.identity.internalURL = http://<%= keystone_server %>:5000/v2.0
catalog.RegionOne.identity.name = Identity Service

Make sure keystone is configured to use a template catalog you should have the following lines in the keystone.conf configuration:

[catalog]
driver = keystone.catalog.backends.templated.TemplatedCatalog
template_file = /etc/keystone/default_catalog.templates

using a DB for the catalog caused heaps of trouble for me..
Hope that helps.

[Anne Gentle (annegentle)]

Marking "won't fix" in lieu of "fix released" because we did add a section about template vs. database for keystone, and this is a fiddly bit that docs try to help with but don't always succeed. :)

[steve A (dafridgie)]

So what actual steps need to be taken to resolve this error ?
I carried out the installation to the letter from this guide - http://docs.openstack.org/trunk/openstack-compute/install/content/

This has been carried out by 2 people independently in our organization and we both end up with this problem
Keystone via command line - no problems, user or tennant management via dashboard has the exact bug as described above:

[Thu May 31 10:43:32 2012] [error] Request returned failure status.
[Thu May 31 10:43:32 2012] [error] Traceback (most recent call last):
[Thu May 31 10:43:32 2012] [error] File "/usr/lib/python2.7/dist-packages/keystoneclient/client.py", line 121, in request
[Thu May 31 10:43:32 2012] [error] body = json.loads(body)
[Thu May 31 10:43:32 2012] [error] File "/usr/lib/python2.7/json/__init__.py", line 326, in loads
[Thu May 31 10:43:32 2012] [error] return _default_decoder.decode(s)
[Thu May 31 10:43:32 2012] [error] File "/usr/lib/python2.7/json/decoder.py", line 369, in decode
[Thu May 31 10:43:32 2012] [error] raise ValueError(errmsg("Extra data", s, end, len(s)))
[Thu May 31 10:43:32 2012] [error] ValueError: Extra data: line 1 column 4 - line 5 column 4 (char 4 - 52)

[Guilherme Birk (guibirk)]

I have the same problem. Tried to follow Omri Siri (omri-o) response an then restart keystone, but nothing changed. I've noticed that the keystone.conf file has more lines using sql, but I don't know if I have to change them too.

[Kevin Jackson (kevin-linuxservices)]

I had the same issue and it turned out that my nova-volume service had an incorrect character in that only came to light when certain features were being called:

VOLUME_PUBLIC_URL="http://$ENDPOINT:8776/v1/\$(tenant_id)s"
VOLUME_ADMIN_URL=$VOLUME_PUBLIC_URL
VOLUME_INTERNAL_URL=$VOLUME_PUBLIC_URL

should be % instead of \$

VOLUME_PUBLIC_URL="http://$ENDPOINT:8776/v1/%(tenant_id)s"

Note there should be no issues using a db backend - Ubuntu packages should work with a MySQL backend.