Comment 1 for bug 1339545

I think this is NOT a bug yet or it should be generalized to the issue of the task reconcilation. You may take a look at https://wiki.openstack.org/TaskFlow.

Check the explantions like "Currently many of the OpenStack components do not handle this forced stop in a way that leaves the state of the system in a reconcilable state. Typically the actions that a service was actively doing are immediately forced to stop and can not be resumed and are in a way forgotten (a later scanning process may attempt to clean up these orphaned resources) " and "TaskFlow will help in this situation by tracking the actions, tasks, and there associated states so that when the service is restarted (even after the services software is upgraded) the service can easily resume (or rollback) the tasks that were interrupted when the stop/kill command was triggered".

OpenStack projects are on their way to refactor with the taskflow. After this is done, it will be possible to make the task recoverable.