Bug 1330292
Summary: | Inconsistent/mistyped option names "ssl-cert-depth", "ssl-cetificate-depth" | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Markus Ueberall <ueberall> | ||||
Component: | transport | Assignee: | Kaleb KEITHLEY <kkeithle> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 3.7.11 | CC: | bugs | ||||
Target Milestone: | --- | Keywords: | Triaged | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-04-26 12:38:15 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: | |||||||
Attachments: |
|
Truncated sentence above: Setting volume option "ssl.certificate-depth" to user-defined value triggers warnings about *unknown option* "transport.socket.ssl-cetificate-depth". *** This bug has been marked as a duplicate of bug 1330249 *** |
Created attachment 1150621 [details] 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