Bug 1475326 - [RFE] get-state CLI should be able to give default volume options values
Summary: [RFE] get-state CLI should be able to give default volume options values
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.1
Assignee: Samikshan Bairagya
QA Contact: Bala Konda Reddy M
URL:
Whiteboard:
Depends On:
Blocks: 1475686
TreeView+ depends on / blocked
 
Reported: 2017-07-26 12:50 UTC by Samikshan Bairagya
Modified: 2017-11-29 03:29 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.8.4-45
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-29 03:29:14 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3276 0 normal SHIPPED_LIVE glusterfs bug fix update 2017-11-29 08:28:52 UTC

Description Samikshan Bairagya 2017-07-26 12:50:09 UTC 
Description of problem:
When you issue a gluster volume get <volname> all command, you can get a list of values set explicitly or by default for all volume options for the particular volume. Support should be added to the get-state CLI to get a list of all volume options too. Currently only the volume options that are explicitly set are shown in the get-state output.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Samikshan Bairagya 2017-07-26 13:13:08 UTC 
Upstream patch: https://review.gluster.org/17858
Comment 3 Atin Mukherjee 2017-09-04 09:38:21 UTC 
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/117182/
Comment 4 Bala Konda Reddy M 2017-10-11 09:12:46 UTC 
BUILD: 3.8.4-48

All the default volume options are getting with gluster get-state 

Hence marking it as verified.
Comment 7 errata-xmlrpc 2017-11-29 03:29:14 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://access.redhat.com/errata/RHBA-2017:3276
Note You need to log in before you can comment on or make changes to this bug.