** Changed in: os-win
       Status: In Progress => Fix Released

** Changed in: compute-hyperv
   Importance: Undecided => Medium

** Changed in: compute-hyperv
     Assignee: (unassigned) => Lucian Petrut (petrutlucian94)

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

  Hyper-V: cannot attach volumes from local HA shares

Status in compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
Status in os-win:
  Fix Released

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

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to