Instances stuck in DELETING state if delete fails

you might try

[root@lljcma mnadmin] # nova reset-state
usage: nova reset-state [--active] <server> [<server> ...]
error: too few arguments
Try 'nova help reset-state' for more information.

and can you provide call back as reference?

Yes, I know you can recover such instances manually, but the whole point is that it would be nice if they recovered automatically after a certain timeout. I intend to work on this.

What do you mean by "call back"?

I mean the error lead to exception, sorry a typo, it should be trace back
usually this kind of bug is handled by nova itself, most error case is we didn't include the right exception
into catch list, so the automatic revert didn't take effect
in case you provide the trace back of exception, it will be much easier to know why the automatic revert didn't work, thanks

The errors is a lost connection to the rabbit, and no, you can't just catch and recover from it, because, well, you don't have connection to the conductor, and so no access to the database to update the state.

I think it would be fine to have another periodic task to handle stuck deleting instances.

Fix proposed to branch: master
Review: https://review.openstack.org/294491

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/294491
Reason: This review is > 6 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments.

Automatically discovered version liberty in description. If this is incorrect, please update the description to include 'nova version: ...'

Fix proposed to branch: master
Review: https://review.openstack.org/598084

Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/598084

I'm not totally sure if this is still an issue given how old this bug is so I'm going to mark it as Incomplete for now. I don't know if restarting the compute service will clean up the instance stuck in DELETING status or not, it would need to be tested (a functional recreate test for something like this would probably be good to exhibit the bug).

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]