nova.compute.utils.get_device_name_for_instance breaks volume attachment on Hyper-V

Bug #1074726 reported by Alessandro Pilotti
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Medium
Unassigned

Bug Description

The following exception is raised in nova.compute.utils.get_device_name_for_instance when trying to attach a Cinder volume on Hyper-V in Grizzly:

DevicePathInUse: The supplied device path (sda3) is in use.

Exception trace details: http://paste.openstack.org/show/24033/

no longer affects: python-glanceclient
Changed in nova:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Joe Gordon (jogo) wrote :

Is this still valid? This was filed against Grizzly and we are now developing Juno

Changed in nova:
status: Confirmed → Incomplete
Sean Dague (sdague)
Changed in nova:
status: Incomplete → Invalid
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.