yahoo-eng-team team mailing list archive

[Xing Yang <1293930@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When doing a block live migration of vm1 from host1 to host2, I found
that the instance directory created on the destination host host2 is not
cleaned up if the migration fails and therefore any future attempt to
migrate vm1 from host1 to host2 will fail because the directory already
exists.

nova live-migration --block-migrate vm1 host2

This following directory will be created to store instance data in pre_live_migration on host2 if the directory doesn't exist:
/opt/stack/data/nova/instances/<instance id for vm1>

If the migration fails after this for some reason, this directory is not
cleaned up.

When you try to do migration again, it fails right away because this
directory already exists.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1293930

Title:
  Instance directory created during live migration are not cleaned up
  after failure

Status in OpenStack Compute (Nova):
  New

Bug description:
  When doing a block live migration of vm1 from host1 to host2, I found
  that the instance directory created on the destination host host2 is
  not cleaned up if the migration fails and therefore any future attempt
  to migrate vm1 from host1 to host2 will fail because the directory
  already exists.

  nova live-migration --block-migrate vm1 host2

  This following directory will be created to store instance data in pre_live_migration on host2 if the directory doesn't exist:
  /opt/stack/data/nova/instances/<instance id for vm1>

  If the migration fails after this for some reason, this directory is
  not cleaned up.

  When you try to do migration again, it fails right away because this
  directory already exists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1293930/+subscriptions