Manila - Manage rule for CIFS share updates status from "error" to "active" for invalid users
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Invalid
|
Low
|
Unassigned | ||
manila-ui |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Pre-conditions:
Devstack with manila plugin is up and running.
HP 3PAR file services backend details are present in /etc/manila/
Steps:
1. Login to Horizon with admin credentials
2. Create a Share type with extra specs as below
snapshot_
share_backend_
thin_provisioni
driver_
*UNITY is HPE 3PAR file services backend.
3. Create a share with above share type and CIFS share protocol.
4. Go to project > share > actions from dropdown and select manage rules for created share.
5. Add a IP access rule for share access.
6. Add a user access rule for a HPE 3PAR user but not from users in file store group. (invalid user)
7. Observe that status for all share access rules changes from 'active' to 'error'.
8. Add a user access rule for user from file store group on HPE 3PAR.(valid user)
9. Observe that status for all share access rules remains as "error".
10. Delete the user access rule for valid user added in step7.
11. Observe that status for all share access rules changes from 'error' to 'active' including for rule for invalid user.
Expected Behavior:
1. After adding a user access rule for invalid user (not from file store group), status for all access rules should not change to 'error'.
2. When there are share access rules for both valid and invalid users, after deleting rule for valid user, rule for invalid user changes from "error" to "active".
Note - Please find screenshot and m-shr.log as attached.
information type: | Private Security → Public |
affects: | manila → manila-ui |
Changed in manila: | |
importance: | Undecided → Low |
Changed in manila: | |
status: | New → Triaged |
summary: |
- Manila UI - Manage rule for CIFS share updates status from "error" to + Manila - Manage rule for CIFS share updates status from "error" to "active" for invalid users |
Attached screenshot for UI.