yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #46685
[Bug 1257723] Re: "Timed out trying to delete user" resolved by heat-engine restart
revocation events (https://blueprints.launchpad.net/keystone/+spec
/revocation-events) has been out for a while now... marking this as fix
released
** Changed in: keystone
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1257723
Title:
"Timed out trying to delete user" resolved by heat-engine restart
Status in heat:
Invalid
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
I left a TripleO overcloud stack running for a couple of days and when
I went to delete it, it went into DELETE_FAILED
| notcomputeConfig | 29 | state changed | DELETE_COMPLETE | 2013-12-04T12:11:25Z |
| CompletionCondition | 30 | state changed | DELETE_COMPLETE | 2013-12-04T12:11:25Z |
| notcompute | 31 | state changed | DELETE_IN_PROGRESS | 2013-12-04T12:11:25Z |
| CompletionHandle | 32 | state changed | DELETE_IN_PROGRESS | 2013-12-04T12:11:32Z |
| CompletionHandle | 33 | Error: Timed out trying to delete user | DELETE_FAILED | 2013-12-04T12:11:42Z |
| notcompute | 34 | Deletion aborted | DELETE_FAILED | 2013-12-04T12:11:42Z |
heat-engine log shows:
Traceback (most recent call last):
File "/opt/stack/venvs/heat/lib/python2.7/site-packages/heat/engine/resource.py", line 575, in delete
handle_data = self.handle_delete()
File "/opt/stack/venvs/heat/lib/python2.7/site-packages/heat/engine/signal_responder.py", line 62, in handle_delete
self.keystone().delete_stack_user(self.resource_id)
File "/opt/stack/venvs/heat/lib/python2.7/site-packages/heat/common/heat_keystoneclient.py", line 302, in delete_stack_user
raise exception.Error(reason)
Error: Timed out trying to delete user
Retrying stack-delete didn't help, until I restarted heat-engine and
it quickly completed
I see we cache the keystone client instance with the stack - any
obvious reason for the client getting foobared in a way that re-
creating it would fix it?
versions:
heat - daddc05
keystone - f72f369
keystoneclient - 7abf8d2
To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1257723/+subscriptions