[Yahoo-eng-team] [Bug 1580122] Re: Hyper-V: cannot attach volumes from local HA shares

2017-06-28 Thread Lucian Petrut 
Fixed in os-brick, no longer affects Nova.

** Changed in: nova
   Status: Triaged => Fix Released

-- 
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 compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
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
  case.

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

-- 
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

[Yahoo-eng-team] [Bug 1580122] Re: Hyper-V: cannot attach volumes from local HA shares

2016-10-17 Thread Claudiu Belu 
** 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).
https://bugs.launchpad.net/bugs/1580122

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

Status in compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
  Triaged
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
  case.

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

-- 
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

[Yahoo-eng-team] [Bug 1580122] Re: Hyper-V: cannot attach volumes from local HA shares

2016-05-24 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/314513
Committed: 
https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=b964f2bce3f3eeac3659e5ef50f520ee1da4afb0
Submitter: Jenkins
Branch:master

commit b964f2bce3f3eeac3659e5ef50f520ee1da4afb0
Author: Lucian Petrut 
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: I8e4426b3b1044d24563adf7826ab9f141c2495b8
Closes-Bug: #1580122

Change-Id: Ib736b39f3bfa58b2737647de23f741ffcf85180b


** Changed in: compute-hyperv
   Status: New => Fix Released

-- 
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 compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
  Triaged
Status in os-win:
  Confirmed

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/compute-hyperv/+bug/1580122/+subscriptions

-- 
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

[Yahoo-eng-team] [Bug 1580122] Re: Hyper-V: cannot attach volumes from local HA shares

2016-05-16 Thread Claudiu Belu 
Addressed on master (os-win): https://review.openstack.org/#/c/314490

** Also affects: os-win
   Importance: Undecided
   Status: New

** Changed in: os-win
   Importance: Undecided => Medium

** Changed in: os-win
 Assignee: (unassigned) => Lucian Petrut (petrutlucian94)

** Changed in: os-win
   Status: New => Confirmed

-- 
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 compute-hyperv:
  New
Status in OpenStack Compute (nova):
  Triaged
Status in os-win:
  Confirmed

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/compute-hyperv/+bug/1580122/+subscriptions

-- 
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

[Yahoo-eng-team] [Bug 1580122] Re: Hyper-V: cannot attach volumes from local HA shares

2016-05-10 Thread Lucian Petrut 
** Also affects: compute-hyperv
   Importance: Undecided
   Status: New

-- 
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 compute-hyperv:
  New
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/compute-hyperv/+bug/1580122/+subscriptions

-- 
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