Keystone token error during concurrent heat template launch

asked 2015-11-01 17:41:20 -0500

monicar gravatar image


I am attempting to concurrently launch 2 Heat templates in two different projects. The template launches multiple server instances and adds them to a loadbalancer pool. Almost everytime I try this at least one of the Heat stacks fails. The failures is due to interactions between Nova and Glance or Neutron ending with an authentication error. Keystone logs show the following token error:

2015-11-01 15:11:24.325225 10447 WARNING keystone.common.wsgi [-] Could not find token: cff05dbf266146d9957be52f8135c49e

The above error is being raised from keystone.token.persistence.backends.sql.Token get_token method. This method gets a None value back when it attempts to retrieve the token from the DB. Prior to the error occurring, I see that this method is used successfully to retrieve the same token several times. After the error occurs, I can see the token is still present and is unexpired in the mysql table. So I suspect the token is fine and that there is a problem accessing the DB. Maybe something with the sql alchemy session or DB connection.

I'm stuck on how to dig into this further. Could anyone provide suggestions on any values, conf options, error logs that might provide a bit more info on whats going with the DB access at this point?


edit retag flag offensive close merge delete