Red Hat Bugzilla – Bug 1399598
[USS,SSL] .snaps directory is not reachable when I/O encryption (SSL) is enabled
Last modified: 2017-03-23 01:52:07 EDT
Description of problem: .snaps directory is not created when snapshot is taken in SSl enabled setup with all the VSS plugin present in smb.conf Version-Release number of selected component (if applicable): samba-4.4.6-2.el7rhgs.x86_64 glusterfs-fuse-3.8.4-5.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1.4 node gluster cluster with samba ctdb setup 2.Enable USS & features.show-snapshot-directory 3.Add all the required VSS plugins 4.Create a snapshot & activate the snapshot according to the smb.conf vss plugins 5.Mount samba share in windows and check for .snaps directory Actual results: No .snaps directory is found Expected results: .snaps directory should be present Additional info: Error messages in client log [2016-11-29 05:22:50.766313] E [socket.c:2436:socket_poller] 0-samba-official-snapd-client: client setup failed [2016-11-29 05:22:54.761085] I [socket.c:343:ssl_setup_connection] 0-samba-official-snapd-client: peer CN = dhcp43-214.lab.eng.blr.redhat.com [2016-11-29 05:22:54.761126] I [socket.c:346:ssl_setup_connection] 0-samba-official-snapd-client: SSL verification succeeded (client: 127.0.0.1:24007) [2016-11-29 05:22:54.762038] I [rpc-clnt.c:1947:rpc_clnt_reconfig] 0-samba-official-snapd-client: changing port to 49154 (from 0) [2016-11-29 05:22:54.778722] E [socket.c:3097:socket_connect] 0-samba-official- snapd-client: connection attempt on 127.0.0.1:24007 failed, (Connection refused)
upstream mainline patch http://review.gluster.org/15979 posted for review.
Upstream master : http://review.gluster.org/15979 Upstream release 3.7 : http://review.gluster.org/15988 Upstream release 3.8 : http://review.gluster.org/15986 Upstream release 3.9 : http://review.gluster.org/15987 Downstream Patch : https://code.engineering.redhat.com/gerrit/91854
.snaps directory is accessible /visible , when SSL is enabled on volume. bug verified on build glusterfs-3.8.4-10.el7rhgs.x86_64
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-0486.html