Description of problem: An acl can be set using GF_POSIX_ACL_*_KEY xattr without notifying the access-control translator. So evenif an acl is set correctly at the backend, it might not work properly because access-control holds wrong acl information in its context about that file. Version-Release number of selected component (if applicable): mainline How reproducible: always Actual results: Expected results: Additional info: This issue identified in only nfs-ganesha acl conversion.
REVIEW: http://review.gluster.org/11144 (access-control : validating context of access control translator) posted (#1) for review on master by jiffin tony Thottan (jthottan)
*** Bug 1226807 has been marked as a duplicate of this bug. ***
REVIEW: http://review.gluster.org/11144 (access-control : validating context of access control translator) posted (#3) for review on master by jiffin tony Thottan (jthottan)
REVIEW: http://review.gluster.org/11144 (access-control : validating context of access control translator) posted (#5) for review on master by jiffin tony Thottan (jthottan)
REVIEW: http://review.gluster.org/11144 (access-control : validating context of access control translator) posted (#6) for review on master by jiffin tony Thottan (jthottan)
REVIEW: http://review.gluster.org/11144 (access-control : validating context of access control translator) posted (#7) for review on master by jiffin tony Thottan (jthottan)
REVIEW: http://review.gluster.org/11144 (access-control : validating context of access control translator) posted (#9) for review on master by jiffin tony Thottan (jthottan)
REVIEW: http://review.gluster.org/11144 (access-control : validating context of access control translator) posted (#10) for review on master by jiffin tony Thottan (jthottan)
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user