Bug 1371475

Summary: [RFE] : Support SSL enabled volume via NFS Ganesha
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: rjoseph
Component: nfs-ganeshaAssignee: rjoseph
Status: CLOSED ERRATA QA Contact: Ambarish <asoman>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: amukherj, asoman, bmohanra, jthottan, rcyriac, rhinduja, rhs-bugs, rjoseph, rtalur, sabose, sasundar, skoduri, storage-qa-internal
Target Milestone: ---Keywords: FutureFeature
Target Release: RHGS 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.8.4-1 Doc Type: Enhancement
Doc Text:
Red Hat Gluster Storage now provides support for NFS-Ganesha to enable Transport Layer Security (SSL) on a management connection between the Ganesha and glusterd services. Libgfapi now checks for the /var/lib/glusterd/secure-access file before making an RPC connection and enables SSL on the management connection if the file is present.
Story Points: ---
Clone Of: 1340608 Environment:
Last Closed: 2017-03-23 05:46:08 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:    
Bug Blocks: 1311843, 1351503, 1351530, 1362602, 1371650    

Comment 2 rjoseph 2016-08-30 17:42:05 UTC
Following patch fixes both BZ 1371475 and BZ 1340608

Upstream Master: 

http://review.gluster.org/15072 - Merged
http://review.gluster.org/15073 - Merged

Uostream release-3.8:
http://review.gluster.org/15361 - Post
http://review.gluster.org/15359 - Post

Comment 7 Ambarish 2017-01-30 06:49:27 UTC
Uptil 3.1.3 Ganesha mounts were failing on an SSL enabled setup.


v3/v4 Mounts work fine now with 3.2 bits,basic IO works fine.

Moving the RFE to Verified.

Will open BZs to track failures(if any,during the regression cycle) on more complex tests .

Comment 10 errata-xmlrpc 2017-03-23 05:46:08 UTC
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

Comment 11 Red Hat Bugzilla 2023-09-14 03:30:18 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days