Windows: cannot handle UNC paths containing subdirs

[Lucian Petrut]

When using Scale-Out File Server SMB shares, we have to use the local share paths instead of the UNC paths, if the host is part of the cluster. There's an os-win method that allows fetching the shared path, but it expects the share name, while we're passing subdirs as well, for which reason it fails with with "Exception during mounting: Could not find the local share path for csv1\volumes.".

We'll have to make sure we're passing the share name only, appending the subdir afterwards.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/620253

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/620253
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=d5c3f3a7f61c6ea48152d16a21b89ca0e0d642c9
Submitter: Zuul
Branch: master

commit d5c3f3a7f61c6ea48152d16a21b89ca0e0d642c9
Author: Lucian Petrut <email address hidden>
Date: Mon Nov 26 16:40:23 2018 +0200

    Windows SMBFS: fix using share subdirs

    When using Scale-Out File Server SMB shares, we have to use the local
    share paths instead of the UNC paths if the host is part of the
    cluster.

    There's an os-win method that allows fetching the shared path but
    it expects the share name, while we're passing subdirs as well,
    for which reason it fails.

    We'll have to make sure we're passing the share name only, appending
    the subdir afterwards.

    Closes-Bug: #1805341

    Change-Id: I47d7e7afefe050cd4b25435cfcfc3e8963bd04bc

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-brick 2.7.0 release.