The basic functionality of VFS is working that includes 1. Setup, Gluster cluster of 192.168.122.13, 192.168.122.14, 192.168.122.15 . In smb.conf on Server 192.168.122.13, you can have a. glusterfs:volfile_server = <invalid server> 192.168.122.13 192.168.122.14 192.168.122.15 Expected result: connection should succeed with 192.168.122.13 . b. glusterfs:volfile_server = <invalid server> 192.168.122.31 192.168.122.14 192.168.122.15 Expected result: connection should succeed with 192.168.122.14 . c. glusterfs:volfile_server = tcp+192.168.122.14:24007 192.168.122.15 Expected result: connection should succeed with 192.168.122.14 . e. glusterfs:volfile_server = 192.168.122.31 192.168.122.44 192.168.122.45 Expected result: connection should fail with log saying could not fetch version -------- samba-client-libs-4.4.6-2.el7rhgs.x86_64 samba-client-4.4.6-2.el7rhgs.x86_64 samba-common-tools-4.4.6-2.el7rhgs.x86_64 samba-winbind-modules-4.4.6-2.el7rhgs.x86_64 samba-common-4.4.6-2.el7rhgs.noarch samba-vfs-glusterfs-4.4.6-2.el7rhgs.x86_64 samba-winbind-4.4.6-2.el7rhgs.x86_64 samba-winbind-clients-4.4.6-2.el7rhgs.x86_64 samba-4.4.6-2.el7rhgs.x86_64 samba-libs-4.4.6-2.el7rhgs.x86_64 samba-debuginfo-4.4.6-2.el7rhgs.x86_64 samba-common-libs-4.4.6-2.el7rhgs.x86_64 samba-winbind-krb5-locator-4.4.6-2.el7rhgs.x86_64 glusterfs-3.8.4-4.el7rhgs.x86_64 glusterfs-geo-replication-3.8.4-4.el7rhgs.x86_64 glusterfs-fuse-3.8.4-4.el7rhgs.x86_64 glusterfs-api-3.8.4-4.el7rhgs.x86_64 python-gluster-3.8.4-4.el7rhgs.noarch glusterfs-debuginfo-3.8.4-4.el7rhgs.x86_64 gluster-nagios-addons-0.2.8-1.el7rhgs.x86_64 samba-vfs-glusterfs-4.4.6-2.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-4.el7rhgs.x86_64 glusterfs-server-3.8.4-4.el7rhgs.x86_64 glusterfs-rdma-3.8.4-4.el7rhgs.x86_64 glusterfs-cli-3.8.4-4.el7rhgs.x86_64 glusterfs-libs-3.8.4-4.el7rhgs.x86_64 gluster-nagios-common-0.2.4-1.el7rhgs.noarch glusterfs-events-3.8.4-4.el7rhgs.x86_64 vdsm-gluster-4.17.33-1.el7rhgs.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0495.html