[volume-attach] there is no relation between 'device' argument to the actual device name inside the guest

Bug #1023966 reported by David Naori
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Undecided
Unassigned

Bug Description

libvirt does not guarantee a correlation between target device to the actual device inside the guest:

# virsh attach-device 264 /tmp/disk
# cat /tmp/disk
<disk type='block' device='disk'>
  <driver name='qemu' type='raw' cache='none'/>
  <source dev='/dev/disk/by-path/ip-10.35.97.20:3260-iscsi-iqn.2010-10.org.openstack:volume-00000002-lun-1'/>
  <target dev='vdk' bus='virtio'/>
  <alias name='virtio-disk2'/>
  <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</disk>

guest OS (f16):

#cat /proc/partitions

major minor #blocks name

 252 0 10241024 vda
 252 1 960 vda1
 252 2 9765625 vda2
 252 96 10485760 vdg

*vdk was created as vdg.

See launchpad question: https://answers.launchpad.net/nova/+question/165695

Revision history for this message
Pádraig Brady (p-draigbrady) wrote :

There might be a possiblity to improve the situation through boot time config (injection, cloud-init).

At least the documentation/client/dash should indicate that this attribute is just a hint

Changed in nova:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.