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.
Closes-Bug: #1580122
(cherry-picked from b964f2bce3f3eeac3659e5ef50f520ee1da4afb0)
Change-Id: Ib736b39f3bfa58b2737647de23f741ffcf85180b
Reviewed: https:/ /review. openstack. org/320438 /git.openstack. org/cgit/ openstack/ compute- hyperv/ commit/ ?id=313967e03ab 65eb6dc6882daf8 703b578a84337e
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 313967e03ab65eb 6dc6882daf8703b 578a84337e
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.
Closes-Bug: #1580122
(cherry-picked from b964f2bce3f3eea c3659e5ef50f520 ee1da4afb0) b2737647de23f74 1ffcf85180b
Change-Id: Ib736b39f3bfa58