Bug 1113476 - [SNAPSHOT] : gluster volume info should not show the value which is not set explicitly
Summary: [SNAPSHOT] : gluster volume info should not show the value which is not set e...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Sachin Pandit
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On:
Blocks: 1113510 1141639 1145020
TreeView+ depends on / blocked
 
Reported: 2014-06-26 09:20 UTC by Sachin Pandit
Modified: 2016-02-15 06:49 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.7.0
Clone Of:
: 1113510 1145020 (view as bug list)
Environment:
Last Closed: 2015-05-14 17:26:06 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Sachin Pandit 2014-06-26 09:20:40 UTC
Description of problem:

Currently snap-max-hard-limit, snap-max-soft-limit, and auto-delete
values are getting displayed in gluster volume info even though they
are not set explicitly.


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


How reproducible:
1/1

Steps to Reproduce:
1. create a volume
2. gluster volume info

Actual results:
Even though value is not set explicitly, they are getting displayed.

Expected results:
Default values should not be displayed in gluster volume info.
Display the value only when it is set explicitly by user.


Additional info:
[root@snapshot-24 glusterfs]# gluster v i
 
Volume Name: vol1
Type: Distribute
Volume ID: 0e2113bc-4489-4d38-a2a0-b31ddba76ec2
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 10.70.43.192:/brick0/b0
Options Reconfigured:
features.barrier: disable
snap-max-hard-limit: 100
snap-max-soft-limit: 90
auto-delete: enable
 
Volume Name: vol2
Type: Distribute
Volume ID: 1d76568a-50d4-418d-bff3-12b33ce972be
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 10.70.43.192:/brick4/b4
Options Reconfigured:
features.barrier: disable
snap-max-hard-limit: 100
snap-max-soft-limit: 90
auto-delete: enable
------------------------------------------------------

Comment 1 Anand Avati 2014-06-27 11:34:16 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit and soft-limit and auto-delete value in gluster volume info.) posted (#1) for review on master by Sachin Pandit (spandit)

Comment 2 Anand Avati 2014-06-30 09:37:01 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit and soft-limit and auto-delete value in gluster volume info.) posted (#2) for review on master by Sachin Pandit (spandit)

Comment 3 Anand Avati 2014-07-01 10:33:11 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit and soft-limit and auto-delete value in gluster volume info.) posted (#3) for review on master by Sachin Pandit (spandit)

Comment 4 Anand Avati 2014-07-03 06:15:34 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#4) for review on master by Sachin Pandit (spandit)

Comment 5 Anand Avati 2014-07-03 06:17:44 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#5) for review on master by Sachin Pandit (spandit)

Comment 6 Anand Avati 2014-07-15 06:01:52 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#6) for review on master by Sachin Pandit (spandit)

Comment 7 Anand Avati 2014-07-15 09:18:44 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#7) for review on master by Sachin Pandit (spandit)

Comment 8 Anand Avati 2014-07-15 10:26:30 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info) posted (#8) for review on master by Sachin Pandit (spandit)

Comment 9 Anand Avati 2014-07-15 19:08:44 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#9) for review on master by Sachin Pandit (spandit)

Comment 10 Anand Avati 2014-07-16 10:19:57 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#10) for review on master by Sachin Pandit (spandit)

Comment 11 Anand Avati 2014-07-17 05:52:39 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#11) for review on master by Sachin Pandit (spandit)

Comment 12 Anand Avati 2014-07-18 06:15:29 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#12) for review on master by Sachin Pandit (spandit)

Comment 13 Anand Avati 2014-07-18 10:25:14 UTC
REVIEW: http://review.gluster.org/8191 (cli/snapshot : Dont display the snapshot hard-limit, soft-limit and auto-delete value in gluster volume info.) posted (#13) for review on master by Sachin Pandit (spandit)

Comment 14 Anand Avati 2014-07-24 10:04:00 UTC
COMMIT: http://review.gluster.org/8191 committed in master by Kaushal M (kaushal) 
------
commit 00bcf8e80bd65de7a8a102b137d35af3ba2cc3c1
Author: Sachin Pandit <spandit>
Date:   Thu Jun 26 07:51:02 2014 +0530

    cli/snapshot : Dont display the snapshot hard-limit, soft-limit
    and auto-delete value in gluster volume info.
    
    Problem : Even though snap-max-hard-limit, snap-max-soft-limit and
    auto-delete values were not set explicitly, It was getting showed
    in the output of gluster volume info.
    
    Solution : Check if the value is already present in dictionary
    (That means, it is set), If value is not present then consider
    the default value,
    
    NOTE : This patch doesn't solve the problem where the values
    which is set globally are being displayed in gluster volume info
    
    Change-Id: I61445b3d2a12eb68c38a19bea53b9051ad028050
    BUG: 1113476
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/8191
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Avra Sengupta <asengupt>
    Reviewed-by: Raghavendra Bhat <raghavendra>
    Reviewed-by: Kaushal M <kaushal>

Comment 15 Niels de Vos 2015-05-14 17:26:06 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 16 Niels de Vos 2015-05-14 17:35:27 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 17 Niels de Vos 2015-05-14 17:37:49 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 18 Niels de Vos 2015-05-14 17:42:30 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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