I think the issue here is the neutronclient should handle re-using
tokens when possible. In general I don't see why it should be the user
of a clients job to handle tokens.
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1192383
Title:
Nova creates too many tokens when booting an image
Status in OpenStack Compute (Nova):
Invalid
Status in Python client library for Neutron:
New
Bug description:
Observed in Grizzly stable branch that nova when booting an image creates lot
many keystone tokens.
On analysis found that tokens were created from quantum but nova called
quantum-client APIs.
Currently Keystone does not support token re-issue for same user credentials.
Hence clients must re-use the tokens when possible.
Due to lot many tokens in keystone DB, when we run any keystone command that
involves revoke_tokens keystone becomes unresponsive for a while as it has to
iterate through all tokens in its DB.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1192383/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
