← Back to team overview

openstack team mailing list archive

Re: [Grizzly] NoneType object unsubscriptable while setting up keystone


Look in the bug database, I think there is already an entry for this. user-list works in general, so it has to be something in your environment that is triggering it. If I remember correctly, you are likely using the Admin token. What are the openstack variables in your environment?

On 05/14/2013 08:10 AM, Daniel wrote:

I am currently trying to install Grizzly on a single node running Red Hat Enterprise Linux Server release 6.4, using RedHat's RDO repository (http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/). The related keystone RPM is openstack-keystone-2013.1-1.el6.noarch.

I have followed the instructions from the official documentation (http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/install-keystone.html), without error up to the "keystone-manage db_sync" (included).

After that point, keystone commands return the following error : 'NoneType' object is unsubscriptable. It would appear that the commands work at least in part, since I can see a user directly in the MySQL database after running a "keystone user-create" command, but I still can't list them :

# keystone user-list
'NoneType' object is unsubscriptable

The only changes I've made to the keystone.conf file apart from the log configuration are the connection and admin_token parameters. The mysql connection works correctly from the command line, and it would seem it works for the keystone utility as well since the database is populated.

I've also found nothing remarkable in the keystone log file.

As a side note, trying to install a full Openstack environment with the packstack utility failed with the same error.

Where should I look to get more info on that error?

Thanks in advance,


Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Follow ups