Heat stack was not always deleted
HeatStack.delete() method didn't check stack timestamps before deletion. As a result it couldn't correctly detect the fact that delete already started. So it could get UPDATE_COMPLETE status from last operation instead and fail because it wasn't expected. Closes-Bug: #1548567 Change-Id: I66130f826c6f72562a7c36920b0decae63adf5e0
This commit is contained in:
parent
3d4ee072ac
commit
cafdcb9d48
|
@ -213,8 +213,10 @@ class HeatStack(murano_object.MuranoObject):
|
|||
try:
|
||||
if not self.current(_context):
|
||||
return
|
||||
self._wait_state(_context, lambda s: True)
|
||||
client.stacks.delete(stack_id=self._name)
|
||||
self._wait_state(
|
||||
_context,
|
||||
lambda status: status in ('DELETE_COMPLETE', 'NOT_FOUND'),
|
||||
wait_progress=True)
|
||||
except heat_exc.NotFound:
|
||||
|
|
Loading…
Reference in New Issue