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.
According to the MS docs, this is not supported for SOFS SMB shares.
This is troublesome for the Hyper-C scenario, as Hyper-V will attempt
to modify the image ACLs, making them unusable.
The fix consists in checking if the share is local, and use the
local path in that case.
Reviewed: https:/ /review. openstack. org/314513 /git.openstack. org/cgit/ openstack/ compute- hyperv/ commit/ ?id=b964f2bce3f 3eeac3659e5ef50 f520ee1da4afb0
Committed: https:/
Submitter: Jenkins
Branch: master
commit b964f2bce3f3eea c3659e5ef50f520 ee1da4afb0
Author: Lucian Petrut <email address hidden>
Date: Tue May 10 13:37:07 2016 +0300
Hyper-V: properly handle loopback shares
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.
According to the MS docs, this is not supported for SOFS SMB shares.
This is troublesome for the Hyper-C scenario, as Hyper-V will attempt
to modify the image ACLs, making them unusable.
The fix consists in checking if the share is local, and use the
local path in that case.
Depends-On: I8e4426b3b1044d 24563adf7826ab9 f141c2495b8
Closes-Bug: #1580122
Change-Id: Ib736b39f3bfa58 b2737647de23f74 1ffcf85180b