Manila HSP driver doesnt support adding existent rules after manage

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

Bug Description

HSP Driver fails when trying to add a rule that already exists in backend for a managed share. It returns "Duplicate NFS rules" and change the rule to an ERROR state.
Also, deleting this existent rules created outside Manila would fail too, since deny operation send "share_id + ip" as rule name and it can be not the name provided by the user.

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/366310

Changed in manila:
assignee: nobody → Alyson (alyson-rodrigues-rosa)
status: New → In Progress
Changed in manila:
milestone: none → newton-rc1
importance: Undecided → Medium
Revision history for this message
Rodrigo Barbieri (rodrigo-barbieri2010) wrote :

Talking to Alyson, this bug does not have a workaround, so changed it to High priority. Also, it leads to another bug where any previously existing rules in HSP cannot be removed through manila, hence the share cannot be deleted, stating that the "Object still has children". So, when deleting a share, it should have its previously existing rules removed as well to properly fix this bug.

Changed in manila:
importance: Medium → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

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

commit b29a0e553f44266fbc544f5cb95cf89f6cfd39db
Author: Alyson Rosa <email address hidden>
Date: Tue Sep 6 16:00:29 2016 -0300

    Fix access rules for managed shares in HSP driver

    A share managed in HSP could have some access rules that
    are not in Manila. Trying to add a rule that already exists
    in backend results in an error. Also, rules in backend that
    names are not "share_id + ip" can't be deleted.
    Additionally, if this share has a rule only in backend and not in
    Manila, trying to delete it would fail, because HSP doesn't allow
    delete share when it still has rules.

    Fix it by adding a check in update access when rules already
    exist in backend. Check for access rule name in backend when
    denying access. And cleaning all rules from backend before
    deleting a share to ensure that it has no children in HSP.

    Change-Id: I0c8ee5c47efe22f004692022dd952f301d669b06
    Closes-Bug: #1620756

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 3.0.0.0rc1

This issue was fixed in the openstack/manila 3.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 3.0.0

This issue was fixed in the openstack/manila 3.0.0 release.

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.