Comment 1 for bug 1508096

I hit this one recently, unfortunately I don't have exact steps for reproducer, but rough flow was:
1) deloyed overcloud (tripleo)
2) ran a stack-update operation (openstack overcloud update stack)
3) heat-engine was killed by OOM killer during stack-update
4) I manually updated state of IN_PROGRESS stacks/resources in DB to FAILED
5) restarted heat-engine and ran stack-update again -> at this point stack got stuck in IN_PROGRESS