*_COMPLETE/FAILED status is set too early
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Angus Salkeld |
Bug Description
I run into this fairly often while running heat_integratio
heat_integratio
-------
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/opt/stack/
File "/opt/stack/
File "/opt/stack/
File "/opt/stack/
resp = self._http_
File "/opt/stack/
raise exc.from_
heatclient.
-------
Sometimes, there's considerable time between setting the state of a stack to *_COMPLETE/FAILED and releasing the StackLock associated with it. Since we check for the stack status only, we run into the above error^ when trying to act on the stack.
Here's the log for h-eng:
2015-04-14 02:39:03.310 2107 DEBUG heat.engine.
2015-04-14 02:39:03.310 2107 DEBUG oslo_messaging.
-------
http://
description: | updated |
Changed in heat: | |
assignee: | nobody → Sirushti Murugesan (sirushtim) |
Changed in heat: | |
assignee: | Sirushti Murugesan (sirushtim) → nobody |
Changed in heat: | |
status: | In Progress → Fix Committed |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | liberty-1 → 5.0.0 |
Somewhat related to this bug: https:/ /bugs.launchpad .net/heat/ +bug/1433340