cannot chown on NFS shares created by generic and LVM drivers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
High
|
Rodrigo Barbieri |
Bug Description
Consider following scenario:
1) userA creates share_X and adds RW rule for userA and userB respective IP addresses.
2) userA mounts share_X and creates a folder in it. Folder will have userA ownership.
3) userB mounts share_X and tries to create a folder inside userA's folder. It says permission denied.
4) userB cannot sudo to create the folder, and userA cannot change ownership of own folder to userB or to anonymous.
5) workaround is both users sudo and create folders and files anonymously. Purpose of having users is defeated.
Consider this other scenario:
1) userA creates share_X and adds RW rule for userA and userB respective IP addresses.
2) userA mounts share_X and creates a file in it. File will have userA ownership.
3) userB mounts share_X and tries to edit userA's file. It says permission denied.
4) userB cannot sudo to edit the file, and userA cannot change ownership of own file to userB or to anonymous.
5) workaround is both users sudo and create folders and files anonymously. Purpose of having users is defeated.
Possible solution is use "no_root_squash" when adding NFS access rules.
Changed in manila: | |
importance: | Undecided → Critical |
importance: | Critical → High |
milestone: | none → mitaka-3 |
Fix proposed to branch: master /review. openstack. org/286296
Review: https:/