when deleting instance which is in migrating state, instance files can be stay in destination node forever

Bug #1242961 reported by Yaguang Tang on 2013-10-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description

When trying to delete an instance which is in migrating state, the instance disk files are migrated to the destination prior to the db being updated. If an api delete is called then only source node instance resources will be released i.e. instance disk files and directory are left on destination node forever.

Yaguang Tang (heut2008) on 2013-10-22
Changed in nova:
assignee: nobody → Yaguang Tang (heut2008)
description: updated
Matt Riedemann (mriedem) on 2013-12-08
Changed in nova:
assignee: Yaguang Tang (heut2008) → nobody
status: New → Confirmed
tags: added: libvirt
wanghong (w-wanghong) on 2013-12-10
Changed in nova:
assignee: nobody → wanghong (w-wanghong)

Wouldn't the periodic task clean up the remains of the VM since the db will not be having this VM associated with the destination node?

wanghong (w-wanghong) wrote :

Actually, the rollback method is not just clean up disk resources, other resources such as network will be cleaned up by the rollback method too.

wanghong (w-wanghong) wrote :

The reason of this bug is that the rollback method will be failed because the instance has been deleted by delete api.

wanghong (w-wanghong) on 2013-12-19
Changed in nova:
assignee: wanghong (w-wanghong) → nobody
Michael Still (mikal) on 2014-03-13
Changed in nova:
importance: Undecided → Low
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers