← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1299368] [NEW] the instance boot-from-volume evacuate failed

 

Public bug reported:


I tested the "nova evacuate" command and found a problem.
My operation steps are as below: 
1.I created a volume on Cinder while cinder using lvm driver, and then launched a instance from the volume on host A. 
2.When host A is broken down(or the compute service down), I use "nova evacuate instanceid-xxx  new-host-name-B" command to resume the instance.
3.The instance launched failed on host B.I checked the libvirt xml, and found the diffrence as below:
the instance xml on A:


   <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source dev='/dev/disk/by-path/ip-186.100.8.144:3260-iscsi-iqn.2010-10.org.openstack:volume-458e9b32-7f65-41ea-823f-9cffcfe4f2b8-lun-1'/>
      <target dev='vda' bus='virtio'/>
      <serial>458e9b32-7f65-41ea-823f-9cffcfe4f2b8</serial>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    
the instance xml on B:
  
   <disk type="file" device="disk">
      <driver name="qemu" type="qcow2" cache="none"/>
      <source file="/var/lib/nova/instances/b059ed87-6029-45c2-a36c-c7d48f64ad61/disk"/>
      <target bus="virtio" dev="vda"/>
    </disk>

** 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/1299368

Title:
  the instance boot-from-volume evacuate failed

Status in OpenStack Compute (Nova):
  New

Bug description:
  
  I tested the "nova evacuate" command and found a problem.
  My operation steps are as below: 
  1.I created a volume on Cinder while cinder using lvm driver, and then launched a instance from the volume on host A. 
  2.When host A is broken down(or the compute service down), I use "nova evacuate instanceid-xxx  new-host-name-B" command to resume the instance.
  3.The instance launched failed on host B.I checked the libvirt xml, and found the diffrence as below:
  the instance xml on A:

  
     <disk type='block' device='disk'>
        <driver name='qemu' type='raw' cache='none'/>
        <source dev='/dev/disk/by-path/ip-186.100.8.144:3260-iscsi-iqn.2010-10.org.openstack:volume-458e9b32-7f65-41ea-823f-9cffcfe4f2b8-lun-1'/>
        <target dev='vda' bus='virtio'/>
        <serial>458e9b32-7f65-41ea-823f-9cffcfe4f2b8</serial>
        <alias name='virtio-disk0'/>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
      </disk>
      
  the instance xml on B:
    
     <disk type="file" device="disk">
        <driver name="qemu" type="qcow2" cache="none"/>
        <source file="/var/lib/nova/instances/b059ed87-6029-45c2-a36c-c7d48f64ad61/disk"/>
        <target bus="virtio" dev="vda"/>
      </disk>

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


Follow ups

References