Description of problem: Both nfs4_getfal/nfs4_setfacl is not working on latest ganesha builds. On the getattr/setattr call at FSAL_GLUSTER condition for acl enabled is always bypassing(glfs_h_acl_set/get is never called) Version-Release number of selected component (if applicable): nfs-ganesha How reproducible: always Steps to Reproduce: 1.Create and Start glusterfs volume 2.Export the volume 3.Enable acl for that volume 4.Mount the volume 5.Create a file and call nfs4_getfacl on that file Actual results: Returns NULL Expected results: Should Return default values Additional info:
Fixes submitted so far: https://review.gerrithub.io/299006 https://review.gerrithub.io/299040
With the latest ganesha build provided, the ACLs functionalities have been working well esp., nfs4_getfacl and nfs4_setfacl work as expected. Moving this bug to ON_QA. [root@dhcp35-197 ~]# nfs4_getfacl /mnt/dir1/ A::OWNER@:rwaDxtTcCy A::GROUP@:rwaDxtcy A::EVERYONE@:rxtcy
Verified with latest build, the nfs4_setfacl and nfs4_getfacl is listing default acls properly on nfsv4 mount. nfs4_setfacl -a A::alice:RX abc nfs4_getfacl abc A::OWNER@:rwaxtTcCy A::alice:rwaxtcy A::GROUP@:rwaxtcy A::EVERYONE@:rwaxtcy nfs-ganesha-2.4.1-1.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.1-1.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-5.el7rhgs.x86_64 Moving the BZ to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2017-0493.html