yahoo-eng-team team mailing list archive

[Dan Genin <daniel.genin@xxxxxxxxxx>]

Migrating instances that have no root disk indeed does not copy data to
the target host. This, however, is probably the expected behavior.
Instances with a non-zero size root disk migrate as expected.

My apologies for not catching this before.

** Changed in: nova
       Status: New => Invalid

-- 
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/1270305

Title:
  LVM backed instance migration does not copy disk

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  When an LVM backed instance is migrated (in Devstack) the instance's
  disk is not copied to the destination compute node and the is not
  deleted from the source compute node.

  Observed with nova 3912d7aae21dfff5a42dd71bd45ef5c5f3b1a82b and
  devstack 78411958fd086acc0270c2380dd61f03ebd1f451. Devstack was setup
  for a multi-node config following directions at
  http://devstack.org/guides/multinode-lab.html.

  LVM backend configured with
  [libvirt]
  images_type = lvm
  images_volume_group = nova-lvm

  To reproduce the bug
  1. Launch an instance
  2. Create a test file and sync the disk in the instance
  4. Sync the disk on the host and verify that the test file was written to disk by grepping the strings in /dev/nova-lvm/instance_..._disk for the test file contents
  5. Initiate instance migration using Horizon interface
  6. Confirm migration
  7. On the destination host check that the test file is missing by grepping for it in /dev/nova-lvm/instance_..._disk
  8. Check that the original LVM volume is still there by listing /dev/nova-lvm/

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