yahoo-eng-team team mailing list archive

[Jay Lee <1271780@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

release: stable/havana, 2013.2.1
virt driver: libvirt
volume driver: cinder.volume.san.HpSanISCSIDriver

when excute (live) block migration for vm made by bootable volume, method post_live_migration_at_destination write a libvirt.xml in destination host.
but it missed block disk information so moved libvirt.xml always has a wrong disk information.

example)
$ cinder create --image-id xxxx --display_name cirros_boot_volume 10
it return volume id yyyy

$ nova boot test_vm --flavor 1 --boot-volume yyyy
it makes vm and libvirt.xml has different information from common vm.
...
  <devices>
    <disk type="block" device="disk">
      <driver name="qemu" type="raw" cache="none"/>
      <source dev="/dev/disk/by-path/ip-san_host:3260-iscsi-iqn.xxxx-739918ef-20aa-45ae-8c86-a923d755942a-lun-0"/>
      <target bus="virtio" dev="vda"/>
      <serial>739918ef-20aa-45ae-8c86-a923d755942a</serial>
    </disk>
...

$ nova live-migration --block-migrate <vm uuid> <destination host>
After migrate, libvirt.xml at destination host has common disk information.
...
  <devices>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2" cache="none"/>
      <source file="/var/lib/nova/instances/c59f0510-1549-4249-993c-0fb79cc2ccab/disk"/>
      <target bus="virtio" dev="vda"/>
    </disk>
...

** Affects: nova
     Importance: Undecided
     Assignee: Jay Lee (hyangii)
         Status: New


** Tags: libvirt

** Tags added: libvirt

** Changed in: nova
     Assignee: (unassigned) => Jay Lee (hyangii)

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

Title:
  block live migration writes wrong libvirt.xml

Status in OpenStack Compute (Nova):
  New

Bug description:
  release: stable/havana, 2013.2.1
  virt driver: libvirt
  volume driver: cinder.volume.san.HpSanISCSIDriver

  when excute (live) block migration for vm made by bootable volume, method post_live_migration_at_destination write a libvirt.xml in destination host.
  but it missed block disk information so moved libvirt.xml always has a wrong disk information.

  example)
  $ cinder create --image-id xxxx --display_name cirros_boot_volume 10
  it return volume id yyyy

  $ nova boot test_vm --flavor 1 --boot-volume yyyy
  it makes vm and libvirt.xml has different information from common vm.
  ...
    <devices>
      <disk type="block" device="disk">
        <driver name="qemu" type="raw" cache="none"/>
        <source dev="/dev/disk/by-path/ip-san_host:3260-iscsi-iqn.xxxx-739918ef-20aa-45ae-8c86-a923d755942a-lun-0"/>
        <target bus="virtio" dev="vda"/>
        <serial>739918ef-20aa-45ae-8c86-a923d755942a</serial>
      </disk>
  ...

  $ nova live-migration --block-migrate <vm uuid> <destination host>
  After migrate, libvirt.xml at destination host has common disk information.
  ...
    <devices>
      <disk type="file" device="disk">
        <driver name="qemu" type="qcow2" cache="none"/>
        <source file="/var/lib/nova/instances/c59f0510-1549-4249-993c-0fb79cc2ccab/disk"/>
        <target bus="virtio" dev="vda"/>
      </disk>
  ...

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