Bug 1300648 - Global options obtained using 'gluster volume get', should not require specific volume name
Global options obtained using 'gluster volume get', should not require specif...
Status: CLOSED WONTFIX
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
mainline
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Muthu Vigneshwaran
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-21 06:03 EST by SATHEESARAN
Modified: 2017-01-23 00:19 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-23 00:19:20 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description SATHEESARAN 2016-01-21 06:03:00 EST
Description of problem:
-----------------------
Global volume options are set using 'gluster volume set' with the volume name set as 'all'. But the same options are obtained using 'gluster volume get' by using the volume name.

In other words, 'gluster volume get' functionality should also use 'all' to obtain the global volume options.

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

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Try to get the global volume option
# gluster volume get <vol-name> op-version

Actual results:
---------------
'gluster volume get' uses specific volume name to get the global volume option

Expected results:
-----------------
'gluster volume get' should implement 'all' as the volume name to obtain the global volume option
Comment 1 Atin Mukherjee 2017-01-23 00:19:20 EST
Patch http://review.gluster.org/15563 has fixed this issue and will be available as part of release-3.10, we'd not be backporting this patch to previous releases and hence closing this issue.

Note You need to log in before you can comment on or make changes to this bug.