Hyper-V volume attach issue: wrong SCSI slot is selected
Bug #1329764 reported by
Lucian Petrut
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Claudiu Belu | ||
Icehouse |
Fix Released
|
Low
|
Denis |
Bug Description
When attaching volumes, the Hyper-V driver selects the slot on the SCSI controller by using the number of drives attached to that controller.
This leads to exceptions when detaching volumes having lower numbered slots and then attaching a new volume.
Take for example 2 volumes attached which will have 0 and 1 as controller addresses. If the first one gets detached, the next time we'll try to attach a volume the controller address 1 will be used (as it's the number of drives attached to the controller at that time) but that slot is actually uesd, so it will raise an exception.
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in nova: | |
assignee: | Petrut Lucian (petrutlucian94) → Claudiu Belu (cbelu) |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 99962/