Public bug reported:
we are using OpenStack Queens:
nova-common/xenial,now 2:17.0.9-6~u16.01+mcp189 all [installed]
nova-compute/xenial,now 2:17.0.9-6~u16.01+mcp189 all [installed,automatic]
nova-compute-kvm/xenial,now 2:17.0.9-6~u16.01+mcp189 all [installed]
guest vm uses windows 2012 datacenter edition
after successfully executing openstack server add volume ${instance_id}
${volume_id}, we observe volume status has changed to in-used and
attachments info are correctly stored in both nova and neutron. But
device does not show up in guest machine.
we execute `virsh dumpxml ${instance_id}` but device is not there. We
then try to edit directly by executing `virsh edit ${instance_id}` and
we see the device with proper attachments info...
At last we have to shutdown the vm and boot again to solve the problem.
command line outputs are put below,
/var/lib/libvirt/qemu# virsh dumpxml 55 --inactive
....
<disk type='network' device='disk'>
<driver name='qemu' type='raw' cache='writeback' discard='unmap'/>
<target dev='vdc' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07'
function='0x0'/>
</disk>
.....
# virsh domblklist 55
Target Source
------------------------------------------------
vda vms/xxx
vdb vms/xxxx
manually attach vdc reports `vdc` in-used
** 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/1836681
Title:
attach volume succeeded but device not found on guest machine
Status in OpenStack Compute (nova):
New
Bug description:
we are using OpenStack Queens:
nova-common/xenial,now 2:17.0.9-6~u16.01+mcp189 all [installed]
nova-compute/xenial,now 2:17.0.9-6~u16.01+mcp189 all [installed,automatic]
nova-compute-kvm/xenial,now 2:17.0.9-6~u16.01+mcp189 all [installed]
guest vm uses windows 2012 datacenter edition
after successfully executing openstack server add volume
${instance_id} ${volume_id}, we observe volume status has changed to
in-used and attachments info are correctly stored in both nova and
neutron. But device does not show up in guest machine.
we execute `virsh dumpxml ${instance_id}` but device is not there. We
then try to edit directly by executing `virsh edit ${instance_id}` and
we see the device with proper attachments info...
At last we have to shutdown the vm and boot again to solve the
problem.
command line outputs are put below,
/var/lib/libvirt/qemu# virsh dumpxml 55 --inactive
....
<disk type='network' device='disk'>
<driver name='qemu' type='raw' cache='writeback' discard='unmap'/>
<target dev='vdc' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07'
function='0x0'/>
</disk>
.....
# virsh domblklist 55
Target Source
------------------------------------------------
vda vms/xxx
vdb vms/xxxx
manually attach vdc reports `vdc` in-used
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1836681/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
