"Timed out trying to delete user" resolved by heat-engine restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Identity (keystone) |
Fix Released
|
Wishlist
|
Unassigned |
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-
| CompletionCondition | 30 | state changed | DELETE_COMPLETE | 2013-12-
| notcompute | 31 | state changed | DELETE_IN_PROGRESS | 2013-12-
| CompletionHandle | 32 | state changed | DELETE_IN_PROGRESS | 2013-12-
| CompletionHandle | 33 | Error: Timed out trying to delete user | DELETE_FAILED | 2013-12-
| notcompute | 34 | Deletion aborted | DELETE_FAILED | 2013-12-
heat-engine log shows:
Traceback (most recent call last):
File "/opt/stack/
handle_data = self.handle_
File "/opt/stack/
self.
File "/opt/stack/
raise exception.
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
Just hit this again, but the overcloud stack wasn't running nearly so long:
| CompletionCondition | 80 | state changed | CREATE_COMPLETE | 2013-12- 04T13:29: 53Z | 04T16:32: 07Z | 04T16:32: 18Z |
| CompletionHandle | 87 | state changed | DELETE_IN_PROGRESS | 2013-12-
| CompletionHandle | 88 | Error: Timed out trying to delete user | DELETE_FAILED | 2013-12-