Description of problem:
When trying to add an arbiter with the 3rd server inside an nspawn container, the add-brick fails because something tries to fuse mount the volume.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a replica 2 volume (myvol)
2. Start a docker/nspawn/lxc container and join glusterd to the peer group (we'll call this hostname "fred")
3. gluster volume add-brick myvol replica 3 arbiter 1 fred:/data/brick
Cryptic error message (should also be a bug): volume add-brick: failed: Commit failed on localhost. Please check log file for details.
[2017-02-07 15:39:01.925609] I [MSGID: 100030] [glusterfsd.c:2455:main] 0-/usr/bin/glusterfs: Started running /usr/bin/glusterfs version 3.9.1 (args: /usr/bin/glusterfs --volfile /tmp/myvol.tcp-fuse.vol --client-pid -6 -l /var/log/glusterfs/myvol-add-brick-mount.log /tmp/mntNgw3Ab)
[2017-02-07 15:39:01.925998] E [mount.c:341:gf_fuse_mount] 0-glusterfs-fuse: cannot open /dev/fuse (No such file or directory)
[2017-02-07 15:39:01.926014] E [MSGID: 101019] [xlator.c:433:xlator_init] 0-fuse: Initialization of volume 'fuse' failed, review your volfile again
I expected that all server-side operations were now using libgfapi instead of fuse mounts.
This bug is getting closed because GlusterFS-3.9 has reached its end-of-life .
Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release.
We are not working on getting this working in next releases. Will mark it as DEFERRED, and will revisit after couple of releases.
With latest containers, if you are running it in --privilege mode, we see that the mounts work there.