Comment 6 for bug 1879368

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (stable/train)

Reviewed: https://review.opendev.org/755787
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=226f7e758a0b704e023e6aec0dfd271d9c4d3716
Submitter: Zuul
Branch: stable/train

commit 226f7e758a0b704e023e6aec0dfd271d9c4d3716
Author: silvacarloss <email address hidden>
Date: Fri May 29 23:21:44 2020 +0000

    [NetApp] Fix CIFS promote back issue

    This change fixes the NetApp promote back issue when using CIFS
    protocol. When promoting a replica, the NetApp ONTAP driver
    attempts to create a new CIFS share entity (an access point as
    defined in [1]) for the new active replica. This behavior
    causes a failure since the storage identifies that a current
    backend CIFS share with the same name exists, considering
    that the reffered replica was once the active one.

    This issue is addressed by removing the related CIFS share
    entity when the replica gets promoted.

    [1] https://library.netapp.com/ecmdocs/ECMP1401220/html/GUID-1898D717-A510-4B3D-B2E3-CCDDD5BD0089.html

    Closes-Bug: #1879368
    Change-Id: Id9bdd5df0ff05ea08881dd2c83397f0a367d9945
    (cherry picked from commit c3aed22f9454ca684af45c929be19b8593d55609)
    (cherry picked from commit d2514735141bcf982e4bf043802591b3d017b526)