yahoo-eng-team team mailing list archive

[Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: hyper-v

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1580122

Title:
  Hyper-V: cannot attach volumes from local HA shares

Status in OpenStack Compute (nova):
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1580122/+subscriptions