Comment 18 for bug 1211276

IMO once you've asked Heat to delete a stack, if the heat-engine then dies there's no only no safe way to do an update on it later, there's not even a valid use case for attempting to support that. You already asked for it to be deleted, no do-overs. The only valid operation should be to try to delete it again.

There's clearly a valid use case for wanting to do an update after a create fails, but I am fairly certain that it will not do the Right Thing at the moment. So, unless you have tested it pretty thoroughly and found that it works, I think for now we should prohibit it and add a blueprint to support that later.