Description of problem: With older versions of gluster, say 3.5.3, glusterfs supports setting selinux context over fuse.glusterfs mountpoint. After 3.6.1, it throws an error : "Invalid option: context". The problem is because of a change in mount.glusterfs script. With older versions, it works fine. Version-Release number of selected component (if applicable): How reproducible: Always in versions from 3.6 Steps to Reproduce: http://www.gluster.org/pipermail/gluster-users.old/2015-January/020014.html Actual results: It throws an error "Invalid option: context" Expected results: Inform FUSE that the glusterfs sub-filesystem supports SElinux while passing mount options and allow to set selinux context over the mountpoint. Additional info: When you set selinux context, the same can be verfied in /proc/mounts: vm1:sel /qwe1 fuse.glusterfs rw,context=system_u:object_r:user_home_t:s0,relatime,user_id=0,group_id=0,default_ permissions,allow_other,max_read=131072 0 0
REVIEW: http://review.gluster.org/12858 (fuse: pass default SElinux mount options on to the kernel) posted (#1) for review on master by Niels de Vos (ndevos)
REVIEW: http://review.gluster.org/12858 (fuse: pass default SElinux mount options on to the kernel) posted (#2) for review on master by Niels de Vos (ndevos)
COMMIT: http://review.gluster.org/12858 committed in master by Niels de Vos (ndevos) ------ commit e6046ddc62a61f63d3c2ff2fb450c07c0604e801 Author: Niels de Vos <ndevos> Date: Wed Dec 2 21:19:56 2015 +0100 fuse: pass default SElinux mount options on to the kernel In order to set default SElinux contexts on a Gluster mount, the standard SElinux mount options need to be passed to the kernel. The mount(8) manual page lists "context", "fscontext", "defcontext" and "rootcontext" as valid options. BUG: 1287763 Change-Id: I015fe27e4c6ff36a030e3480b23141aca2d91fc2 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/12858 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Humble Devassy Chirammal <humble.devassy> Reviewed-by: Manikandan Selvaganesh <mselvaga>
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