[Bugs] [Bug 1322211] New: volume get functionality returns null value for few volume options
bugzilla at redhat.com
bugzilla at redhat.com
Wed Mar 30 03:03:32 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1322211
Bug ID: 1322211
Summary: volume get functionality returns null value for few
volume options
Product: GlusterFS
Version: 3.7.9
Component: glusterd
Severity: medium
Assignee: bugs at gluster.org
Reporter: sasundar at redhat.com
CC: bugs at gluster.org
Description of problem:
-----------------------
gluster volume get functionality returns a null value, even those options have
a default value which is non-null value
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gluster-3.7.9
How reproducible:
-----------------
Always
Steps to Reproduce:
-------------------
1. Get the default value of bind-insecure and allow-insecure
# gluster volume get <vol-name> bind-insecure
Actual results:
---------------
gluster volume get returns null value for few option eventhough they have
default options.
The default value of bind-insecure is off, but the volume get returns 'null'
value
Expected results:
-----------------
gluster volume get should get the default value for the options
Additional info:
----------------
I have filtered out the options for which 'gluster volume get' returns null
value. Few of the options the null value looks valid.
For eg, auth.reject & auth.allow - which haven't got any values and its
reasonable to display null values for those
But client.bind-insecure & server.allow-insecure has got a default values and
those should be printed rather than null value
[root at dhcp37-52 ~]# gluster volume get test all | grep \(null\)
cluster.subvols-per-directory (null)
cluster.rsync-hash-regex (null)
cluster.extra-hash-regex (null)
cluster.local-volume-name (null)
cluster.switch-pattern (null)
cluster.read-subvolume (null)
cluster.data-self-heal-algorithm (null)
cluster.quorum-count (null)
diagnostics.brick-logger (null)
diagnostics.client-logger (null)
diagnostics.brick-log-format (null)
diagnostics.client-log-format (null)
encryption.master-key (null)
network.tcp-window-size (null)
network.tcp-window-size (null)
auth.reject (null)
transport.keepalive (null)
server.allow-insecure (null)
features.grace-timeout (null)
server.ssl (null)
server.own-thread (null)
ssl.own-cert (null)
ssl.private-key (null)
ssl.ca-list (null)
ssl.crl-path (null)
ssl.certificate-depth (null)
ssl.cipher-list (null)
ssl.dh-param (null)
ssl.ec-curve (null)
features.limit-usage (null)
debug.exclude-ops (null)
debug.include-ops (null)
debug.error-failure (null)
debug.error-number (null)
debug.error-fops (null)
nfs.exports-auth-enable (null)
nfs.auth-refresh-interval-sec (null)
nfs.auth-cache-ttl-sec (null)
changelog.changelog-dir (null)
features.trash-eliminate-path (null)
locks.trace (null)
client.bind-insecure (null)
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list