Description of problem: Recently NFSv4 ACL support was added to NFS-ganesha for FSAL_GLUSTER. But while using that support, incase if there is no ACL set, and the client issues nfs4_getfacl to read the ACL, we return empty response to the client. Instead we should be constructing a default_acl from the mode-bits and send it to the client as done by Kernel-NFS. Version-Release number of selected component (if applicable): ACLs supported for NFS-Ganesha - FSAL_GLUSTER from version 2.1 onwards.
This is not a major issue but a tracker bug opened by dev. This only helps us better the ACL usage experience. This will be addressed for the next release.
Please review and sign-off edited doc text.
Soumya reviewed the text during online review meeting. Hence removing need_info.
As can be seen that the default is available, [root@rhsauto004 ~]# nfs4_getfacl /mnt/run6067/ A::OWNER@:rwaDxtTcCy A::GROUP@:rxtcy A::EVERYONE@:rxtcy Hence moving this 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/RHSA-2015-1845.html