[Bugs] [Bug 1330292] New: Inconsistent/mistyped option names "ssl-cert-depth", "ssl-cetificate-depth"

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1330292

            Bug ID: 1330292
           Summary: Inconsistent/mistyped option names "ssl-cert-depth",
                    "ssl-cetificate-depth"
           Product: GlusterFS
           Version: 3.7.11
         Component: transport
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: ueberall at projektzentrisch.de
                CC: bugs at gluster.org



Created attachment 1150621
  --> https://bugzilla.redhat.com/attachment.cgi?id=1150621&action=edit
Log excerpts, setup details (before/after modifying the option names)

Description of problem:
Setting volume option "ssl.certificate-depth" to user-defined value triggers
warnings about 

Version-Release number of selected component (if applicable):
3.7.11

How reproducible:
Given volume <vol>, execute "gluster volume set <vol> ssl.certificate-depth 1"

Actual results:
The option value is stored, but not correctly copied elsewhere ("namespace
problem"), triggering the following warning (see attachment for context):
W [graph.c:357:_log_if_unknown_option] 0-webroot-client-<Number>: option 't
ransport.socket.ssl-cetificate-depth' is not recognized

NB it is not clear whether there's another side effect of this inconsistency
(current setup with certificates fails, regardless of value for
ssl.certificate-depth and ssl.cipher-list).

Expected results:
No warning.


Additional info:
The following changes get rid of the warning (resulting configuration is clean,
but a test run still shows the same certificate errors, see bottom of attached
file):
    sed -i 's|ssl-cert-depth|ssl-certificate-depth|g'
rpc/rpc-transport/socket/src/socket.c
xlators/mgmt/glusterd/src/glusterd-volume-set.c
    sed -i 's|ssl-cetificate-depth|ssl-certificate-depth|g'
xlators/mgmt/glusterd/src/glusterd-volgen.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.