← Back to team overview

openstack team mailing list archive

Re: Keystone Grizzly-3 Tokens not getting saved to database

 

Hello Dolph,

Thank you for responding. That was it. I guess the default token driver must have recently changed from sql to kvs.

Mark

From: Dolph Mathews [mailto:dolph.mathews@xxxxxxxxx]
Sent: Friday, March 01, 2013 6:47 AM
To: Miller, Mark M (EB SW Cloud - R&D - Corvallis)
Cc: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] Keystone Grizzly-3 Tokens not getting saved to database

Your keystone.log should have a more complete backtrace of the error -- can you post that?

As for your token table being empty, are you sure you're using the SQL driver (keystone.token.backends.sql.Token)? I believe the default driver is in-memory (keystone.token.backends.kvs.Token). The token table will be created by db_sync regardless of which driver is configured.


-Dolph

On Thu, Feb 28, 2013 at 5:23 PM, Miller, Mark M (EB SW Cloud - R&D - Corvallis) <mark.m.miller@xxxxxx<mailto:mark.m.miller@xxxxxx>> wrote:
Hello,

I have some tests that attempt to retrieve tenants/projects from Keystone using an admin user's token. The test gave the following error:

{"error": {"message": "coercing to Unicode: need string or buffer, NoneType found", "code": 400, "title": "Bad Request"}}

The same code works fine if I use the X-Auth-Token from the keystone.conf file. I checked the database to look at the tokens and found that the "token" table is empty. Does anyone have any ideas as to why tokens are not getting stored on my system? I assume it is some keystone.conf parameter, but I really do not know.

Regards,

Mark

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


References