Bug 1400013

Summary: [USS,SSL] .snaps directory is not reachable when I/O encryption (SSL) is enabled
Product: [Community] GlusterFS Reporter: rjoseph
Component: snapshotAssignee: rjoseph
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: amukherj, ashah, bugs, kaushal, rhs-bugs, rhs-smb, rjoseph, storage-qa-internal, vdas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.10.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1399598
: 1400458 1400459 1400460 (view as bug list) Environment:
Last Closed: 2017-03-06 17:37:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1399598    
Bug Blocks: 1400458, 1400459, 1400460    

Comment 1 Worker Ant 2016-11-30 10:08:05 UTC
REVIEW: http://review.gluster.org/15979 (uss: snapd should enable SSL if SSL is enabled on volume) posted (#1) for review on master by Rajesh Joseph (rjoseph)

Comment 2 Worker Ant 2016-12-01 04:20:05 UTC
REVIEW: http://review.gluster.org/15979 (uss: snapd should enable SSL if SSL is enabled on volume) posted (#2) for review on master by Rajesh Joseph (rjoseph)

Comment 3 Worker Ant 2016-12-01 09:27:11 UTC
COMMIT: http://review.gluster.org/15979 committed in master by Kaushal M (kaushal) 
------
commit 182f0d12040dab5081ca645a3f370f65cd68b528
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.
    
    Change-Id: I0d7fe86c567b297a8528a48faf06161d4c3cb415
    Signed-off-by: Rajesh Joseph <rjoseph>
    BUG: 1400013
    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>

Comment 4 Shyamsundar 2017-03-06 17:37:12 UTC
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.10.0, please open a new bug report.

glusterfs-3.10.0 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-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/