the vms can not be force deleted when vm_status is soft-delete and task-state=deleting

Bug #1875624 reported by xuyuanhao
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
In Progress
Low
xuyuanhao

Bug Description

Description
===========
the vms can not be force deleted when vm_status is soft-delete and task-state=deleting

Steps to reproduce
==================
1.soft delete the vms
2.force delete the vms which status is soft-delete.
3.down the nova-compute while deleting the vms.
4.restart the nova-compute
5.force delete the vms

Expected result
===============
the vms be destoried compeletely

Actual result
=============
can not destory these vms.

Environment
===========
1. OpenStack Rocky version
2.Hypervisor is kvm
3.The storage is Ceph
4.Networking is Neutron with OpenVSwitch

Logs&Configs
============
The logs as following:
Instance is already in deleting state, ignoring this request

Tags: api
Revision history for this message
Brin Zhang (zhangbailin) wrote :

Rocky has the same delete instance logical with master.

Changed in nova:
assignee: nobody → xuyuanhao (thourch)
assignee: xuyuanhao (thourch) → nobody
xuyuanhao (thourch)
Changed in nova:
assignee: nobody → xuyuanhao (thourch)
Revision history for this message
Balazs Gibizer (balazs-gibizer) wrote :

FYI there was an old bug related to this https://bugs.launchpad.net/nova/+bug/1308342 but the fix for that was reverted.

Overall I agree that we should be able to delete the instance even if it is stuck in task_state=DELETING state due to a compute restart. So I confirm the bug.

Changed in nova:
status: New → Confirmed
importance: Undecided → Low
tags: added: api
Changed in nova:
status: Confirmed → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.