Hyper-V driver volumes are attached incorrectly when multiple iSCSI servers are present
Bug #1322926 reported by
Alessandro Pilotti
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Alessandro Pilotti | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hyper-V can change the order of the mounted drives when rebooting a host and thus passthrough disks can be assigned to the wrong instance resulting in a critical scenario.
tags: | added: hyper-v |
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → juno-1 |
Changed in nova: | |
assignee: | nobody → Bora Adrian (abora) |
status: | Triaged → In Progress |
Changed in nova: | |
assignee: | Bora Adrian (abora) → Alessandro Pilotti (alexpilotti) |
Changed in nova: | |
assignee: | Alessandro Pilotti (alexpilotti) → Petrut Lucian (petrutlucian94) |
Changed in nova: | |
assignee: | Petrut Lucian (petrutlucian94) → Alessandro Pilotti (alexpilotti) |
Changed in nova: | |
milestone: | none → juno-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
this is not critical from a nova point of view (though it may be for hyper-v). The priorities should be overall project prio, not individual driver prio