Ubuntu
nova package

  1. Trusty (14.04)
  2. Bug #1374508
  3. Comment #5

Comment 5 for bug 1374508

Revision history for this message
Mitsuhiro Tanino (mitsuhiro-tanino) wrote : Re: Possible race between unrescue and detach

Further investigation there are some differences between normal volume detachment and this error case of volume detachment.

(1) libvirtd.log of Normal volume detach
http://paste.openstack.org/show/202077/

(2) libvirtd.log of this error case during volume detach
http://paste.openstack.org/show/202078/

In the log (1), I can see the following logs which mentions removing the virtio-disk. However, I couldn't see same logs in the log (2).
--- snip ---
2015-04-10 14:46:33.098+0000: 787: debug : qemuProcessHandleDeviceDeleted:1349 : Device virtio-disk1 removed from domain 0x7f7da0026b60 instance-0000002e
2015-04-10 14:46:33.098+0000: 787: debug : qemuDomainRemoveDiskDevice:2444 : Removing disk virtio-disk1 from domain 0x7f7da0026b60 instance-0000002e

Also I confirmed following two points.
(3) Login the instance via ssh after reboot to confirm device list of instance.
(4) Check virsh dumpxml result to confirm the device list of instance.

As for (3), I couldn't see the device file(/dev/vdb) for the Cinder volume. This means that the device was already detached from the viewpoint of qemu-kvm.
As for (4), the Cinder volume configuration still remained in the XML file of the instance.So libvirt kept Cinder volume information even though there was no device in the VM.

Very odd status...