Why glusterfs mount fails at boot when specifying security context option?

Issue

• Unable to mount glusterfs at boot when specifying security context.
• When specifying a SELinux context="system_u:object_r:httpd_sys_rw_content_t:s0" as mount option on client, the mount fails at boot. However it succeeds if mounted manually after login.

[2019-09-06 20:22:58.074578] I [MSGID: 100030] [glusterfsd.c:2646:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.12.2 (args: /usr/sbin/glusterfs --acl --fuse-mountopts=context=""system_u:object_r:httpd_sys_rw_content_t:s0"" --volfile-server=gluster-1 --volfile-id=dist-rep-vol3 --fuse-mountopts=context=""system_u:object_r:httpd_sys_rw_content_t:s0"" --subdir-mount=/loco /var/lib/pulp/content)
[2019-09-06 20:22:58.220974] E [mount.c:444:fuse_mount_sys] 0-glusterfs-fuse: ret = -1

[2019-09-06 20:22:58.221108] I [mount.c:489:gf_fuse_mount] 0-glusterfs-fuse: direct mount failed (Permission denied) errno 13
[2019-09-06 20:22:58.221120] E [mount.c:502:gf_fuse_mount] 0-glusterfs-fuse: mount of gluster-1:dist-rep-vol3/loco to /var/lib/pulp/content (context=""system_u:object_r:httpd_sys_rw_content_t:s0"",allow_other,max_read=131072) failed
[2019-09-06 20:22:58.245740] W [MSGID: 101002] [options.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' is deprecated, preferred is 'transport.address-family', continuing with correction