Windows remotefs: unexpected mountpoint location

[Lucian Petrut]

In order to support running inside a Scale-Out File Server cluster, when 'mounting' a local share, we're creating a symlink to the local export path without actually creating a SMB mapping.

The issue is that instead of creating a symlink using hash of the share UNC path, we're using the local export path instead. This is undesired behavior, in which case the caller will not be able to find the 'mountpoint'.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/383704
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=6b847ffd945044bc86540884230db10873efc731
Submitter: Jenkins
Branch: master

commit 6b847ffd945044bc86540884230db10873efc731
Author: Lucian Petrut <email address hidden>
Date: Fri Oct 7 14:46:00 2016 +0300

    Windows remotefs: create mountpoints at the expected location

    In order to support running inside a Scale-Out File Server cluster,
    when 'mounting' a local share, we're creating a symlink to the local
    export path without actually creating a SMB mapping.

    The issue is that instead of creating a symlink using the hash of
    the share UNC path, we're using the local export path instead. This
    is undesired behavior, in which case the caller will not be able
    to find the 'mountpoint'.

    This change addresses this issue, ensuring that we're using the
    mountpoint expected by the caller (e.g. the Cinder SMB driver)
    when mounting SMB shares.

    Closes-Bug: #1631351

    Change-Id: I6bf909da559a745596f7d4c30d12e794b0b156de

[OpenStack Infra (hudson-openstack)]

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