Hyper-V: cannot attach volumes from local HA shares
Bug #1580122 reported by
Lucian Petrut
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Unassigned | ||
compute-hyperv |
Fix Released
|
Medium
|
Lucian Petrut | ||
os-win |
Fix Released
|
Medium
|
Lucian Petrut |
Bug Description
At the moment, the Hyper-V driver uses the UNC path of images stored on SMB shares, regardless if the share is remote or not. Citing from the MS documentation, this is not supported:
“Accessing a continuously available file share as a loopback share is not supported. For example, if Microsoft SQL Server or Hyper-V store data files on SMB file shares, they must run on computers that are not a member of the file server cluster for the SMB file shares.”
This is troublesome for the Hyper-C scenario, as Hyper-V will attempt to modify the image ACLs, making them unusable. The easy fix is to simply check if the share is local, and use the local path in that case.
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in os-win: | |
status: | In Progress → Fix Released |
Changed in compute-hyperv: | |
importance: | Undecided → Medium |
assignee: | nobody → Lucian Petrut (petrutlucian94) |
To post a comment you must log in.
Addressed on master (os-win): https:/ /review. openstack. org/#/c/ 314490