REVIEW: http://review.gluster.org/15987 (uss: snapd should enable SSL if SSL is enabled on volume) posted (#1) for review on release-3.9 by Rajesh Joseph (rjoseph)
Pasting the bug description here, as the original is private and contains some sensitive information. """ 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) """
COMMIT: http://review.gluster.org/15987 committed in release-3.9 by Kaushal M (kaushal) ------ commit fe65668466895d33a589a4a51c45cc52fcaf14bd Author: Rajesh Joseph <rjoseph> Date: Tue Nov 29 21:57:37 2016 +0530 uss: snapd should enable SSL if SSL is enabled on volume During snapd graph generation we should check if SSL is enabled on main volume or not. This is because clients will communicate with snapd as if it is communicating to a brick. > Reviewed-on: http://review.gluster.org/15979 > Smoke: Gluster Build System <jenkins.org> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Kaushal M <kaushal> (cherry picked from commit 182f0d12040dab5081ca645a3f370f65cd68b528) Change-Id: I0d7fe86c567b297a8528a48faf06161d4c3cb415 Signed-off-by: Rajesh Joseph <rjoseph> BUG: 1400460 Reviewed-on: http://review.gluster.org/15987 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Avra Sengupta <asengupt> Reviewed-by: Kaushal M <kaushal>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.1, please open a new bug report. glusterfs-3.9.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/