Bug 1056028 - Some volume set options are listed twice in the volume set help with inconsistent data.
Summary: Some volume set options are listed twice in the volume set help with inconsis...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.1
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: Atin Mukherjee
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard: glusterd
Depends On: 1005344 1256268
Blocks: 1245168
TreeView+ depends on / blocked
 
Reported: 2014-01-21 12:27 UTC by Vijaykumar Koppad
Modified: 2022-03-13 13:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1245168 (view as bug list)
Environment:
Last Closed: 2015-12-25 08:44:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Vijaykumar Koppad 2014-01-21 12:27:30 UTC
Description of problem: Some volume set options are list twice in the volume set help with inconsistent data.

These are two options,

performance.cache-size - for this option, at one place default value is 32MB and at another its 128MB 
network.tcp-window-size


Version-Release number of selected component (if applicable):glusterfs-3.4.0.57rhs-1


How reproducible: Happens everytime


Steps to Reproduce:
1.run "gluster volume set help"
2.and grep for this two options. 


Actual results: for two options there are two entries and have inconsistent data.


Expected results: Volume set help should have only one entry and show consistent data. 


Additional info:

Comment 3 Atin Mukherjee 2015-04-02 06:12:12 UTC
An upstream patch http://review.gluster.org/#/c/10110/ is posted.

Comment 4 Atin Mukherjee 2015-04-06 04:32:09 UTC
Upstream patch has been committed in master branch. This fix will be ready to be tested once the downstream branching takes place.

Comment 5 Atin Mukherjee 2015-04-10 11:48:43 UTC
The upstream patch doesn't fix the problem.

Comment 6 Dustin Black 2015-07-18 22:23:22 UTC
(In reply to Atin Mukherjee from comment #5)
> The upstream patch doesn't fix the problem.

After this note, the upstream bug was closed noting the problem should be fixed, but there was no additional patch information included.

Can we please confirm whether this the problem resolved in glusterfs 3.7.0?


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