+++ This bug was initially created as a clone of Bug #1330248 +++ Description of problem: from #gluster xlators/mgmt/glusterd/src/glusterd-volgen.c sets volume option ssl-cetificate-depth Which not only is missing the 'r' in certifciate, but over in rpc/rpc-transport/socket/src/socket.c the volume option being looked for is ssl-cert-depth Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14067 (glusterd: SSL certificate depth volume option is incorrect) posted (#1) for review on release-3.7 by Kaleb KEITHLEY (kkeithle)
COMMIT: http://review.gluster.org/14067 committed in release-3.7 by Atin Mukherjee (amukherj) ------ commit 256959e9e4e98a8da041778a9607ee279c46d2e5 Author: Kaleb S KEITHLEY <kkeithle> Date: Mon Apr 25 14:22:07 2016 -0400 glusterd: SSL certificate depth volume option is incorrect Between 3.7.1 and 3.7.2 a typo was introduced changing the string ssl-cert-depth to ssl-cetificate-depth. [sic] rpc/rpc-transport/socket/src/socket.c still expects the string ssl-cert-depth. Also replace a couple errant tabs with spaces. See: > Change-Id: I0621258470bd831c97008b56123a9dc7029d73f1 > BUG: 1330248 > http://review.gluster.org/#/c/14066/ Change-Id: I4d227fc40d9377dd1a1ef39bf31be026ba43acb1 BUG: 1330249 Signed-off-by: Kaleb S KEITHLEY <kkeithle> Reviewed-on: http://review.gluster.org/14067 Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj>
*** Bug 1330292 has been marked as a duplicate of this bug. ***
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.7.12, please open a new bug report. glusterfs-3.7.12 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] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user