HPE3PAR missing filestore can make a share undeletable

[Mark Sturdevant]

When a create share error happens (or if someone does removals on the backend) it is possible that a manila share to be deleted and its filestore do not exist on the backend. In this case, the manila delete should be successful. Currently the missing filestore (which means there is no share) is not handled properly resulting in an exception and a fail to delete.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/336315
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=6f506a87052e315f5f14c1edf6d592d782204b18
Submitter: Jenkins
Branch: master

commit 6f506a87052e315f5f14c1edf6d592d782204b18
Author: mark.sturdevant <email address hidden>
Date: Thu Jun 30 16:04:44 2016 -0700

    HPE3PAR: Handle exceptions on deleted shares

    Fix to ensure that an attempt to delete a manila share will not
    fail because the 3PAR filestore does not exist. When the filestore
    does not exist, that means the share is already gone (or never was
    created). Avoid the delete and all filestore use in this case to
    prevent failures during delete.

    Also catch and log exceptions during the post-delete cleanup.

    Change-Id: I0e477d3dae5706547354bd029b40e3308349fabb
    Closes-Bug: #1597940

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/manila 3.0.0.0b3 development milestone.