migrating instance can be terminated, and data inconsistency occurs

Bug #751242 reported by Kei Masumoto
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Kei Masumoto

Bug Description

Someone report to me below issue.
It is not critical, and not always occur, but should handle someway.

------------------------------------------------------------------------------------------
Steps to reproduce:-
1) create one VM instance on host ubuntu-openstack-compute-01
2) call nova-manage vm live_migration
$nova/bin/nova-manage --flagfile=/etc/nova/nova.conf vm live_migration i-00000035 ubuntu-openstack-compute-01
3) Immediately call euca-terminate-instances i-00000035
4) euca-describe-instances doesn't display instance i-00000035.

I was expecting, the vm instance will be destroyed from the host ubuntu-openstack-compute-01.
But when I enter the command virsh list on ubuntu-openstack-compute-01
$virsh list
Id Name State
----------------------------------
  6 instance-00000035 running

That means, the instance is marked as deleted in the DB, but it didn't destroy the VM instance.
I think this is not correct.
------------------------------------------------------------------------------------------

Related branches

Kei Masumoto (masumotok)
Changed in nova:
status: New → Confirmed
status: Confirmed → In Progress
assignee: nobody → Kei Masumoto (masumotok)
Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Low
Thierry Carrez (ttx)
Changed in nova:
milestone: none → cactus-rc
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: cactus-rc → 2011.2
status: Fix Committed → Fix Released
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.