Huawei: Fix exception in update_access not found

Bug #1585035 reported by zhongjun
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Undecided
zhongjun

Bug Description

When share is deleted in the backend, user is unable to delete
share because of error thrown in update_access(). This
method throws a ShareResourceNotFound exception to be handled
by manager, thus allowing share to be deleted in this case,
without having to use force-delete.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

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

Changed in manila:
assignee: nobody → zhongjun (jun-zhongjun)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.openstack.org/320257
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=548975ee2d372f8374697e3d838e0b62cf2c6310
Submitter: Jenkins
Branch: master

commit 548975ee2d372f8374697e3d838e0b62cf2c6310
Author: zhongjun <email address hidden>
Date: Tue May 24 15:26:01 2016 +0800

    Huawei: Fix exception in update_access not found

    When share is deleted in the backend, user is unable to delete
    share because of error thrown in update_access(). Make backend raise
    ShareResourceNotFound exception in case share not found during
    "update_access" operation, because share manager expects it for
    proper handling of share deletion, thus allowing share to be
    deleted in this case, without having to use force-delete.

    After add ShareResourceNotFound exception, it will need a parameter
    named share id(share['id']), so add share id to share info in
    create_share_from_snapshot function.

    Change-Id: I9756ff882e6960b07f5f0abac94057c687830ad0
    Closes-Bug: #1585035

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/manila 3.0.0.0b1

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.