[Bugs] [Bug 1420027] New: Cannot add-brick with servers in containers.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1420027

            Bug ID: 1420027
           Summary: Cannot add-brick with servers in containers.
           Product: GlusterFS
           Version: 3.9
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: joe at julianfamily.org
                CC: bugs at gluster.org



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):
3.9.1

How reproducible:
always

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

Actual results:
Cryptic error message (should also be a bug): volume add-brick: failed: Commit
failed on localhost. Please check log file for details.

myvol-add-brick-mount.log
---
[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
---

Expected results:
I expected that all server-side operations were now using libgfapi instead of
fuse mounts.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.