-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of use_nfsv4_alcs option in ansible.posix.acl #240
Comments
Or there should be completely new module like |
Thank you for reporting this issue! It seems that this issue wasn't taken over from core to collections for some reason. |
I too would love some nfsv4 love. So what's the desired outcome: two different acl modules (acl and nfs4_acl for example) or do we want to keep everything under the same umbrella? I mean they're sufficiently different enough it'd make sense to have them separated. |
Also having same issue with this module. For our project we use it for both local and nfs file systems. Created this quick patch for now to workaround this nfsv4 issue. We mostly use it for adding group permissions so it all works now. But definitely this module needs to be fixed for the NFS.
|
* Fixes ansible-collections#240 (AAP-29225) Signed-off-by: Hideki Saito <[email protected]>
* Fixed ansible-collections#240 Signed-off-by: Hideki Saito <[email protected]>
Fixed to set ACLs on paths mounted with NFSv4 correctly SUMMARY Fixed to set ACLs on paths mounted with NFSv4 correctly. Fixed #240 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ansible.posix.acl ADDITIONAL INFORMATION None
SUMMARY
There is an option
use_nfsv4_acls: true
which allows to use NFSv4 ACL rules instead of POSIX ones. It does not work at all.It was already mentioned here ansible/ansible#58679, but it has been closed after
ansible.posix
was moved to a separated repo.ISSUE TYPE
COMPONENT NAME
ansible.posix.acl
ANSIBLE VERSION
But the same thing with ansible 2.12 on python 3.7.
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Oracle Linux Server 7.8
Linux 4.14.35-1902.300.11.el7uek.x86_64
STEPS TO REPRODUCE
EXPECTED RESULTS
Users cannot see content of
/shared_folder
, but each user could access to/shared_folder/%username%
ACTUAL RESULTS
The error is raised:
The command which is actually being executed is:
This is caused by this line:
ansible.posix/plugins/modules/acl.py
Lines 180 to 181 in b3e395a
:allow
suffix is added to a command, butsetfacl
accepts only 3 items delimited by:
, not 4:user:me:rwx
NFSv4 ACL does allow 4 items in the rule, but module should use
nfs4_setfacl
/nfs4_getfacl
instead of puresetfacl
/getfacl
.But it's not enough to add another
if
block in the module which will select command name because these 2 set of commands accepts completely different options:nfs4_setfacl
does not allow to pass neither of-m
,--test
--no-mask
options at all.More than that, they are using completely different set of permissions:
And according to this help message
allow
is not the correct one.So my proposal is to completely remove
use_nfsv4_acls
because it cannot be used at all.The text was updated successfully, but these errors were encountered: