Bug 1229180 - Good to use same "scrub-frequency" value across commands
Summary: Good to use same "scrub-frequency" value across commands
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: bitrot
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.1.1
Assignee: Gaurav Kumar Garg
QA Contact: RajeshReddy
URL:
Whiteboard:
Depends On:
Blocks: 1251815 1252702
TreeView+ depends on / blocked
 
Reported: 2015-06-08 08:57 UTC by RajeshReddy
Modified: 2016-09-17 14:22 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1252702 (view as bug list)
Environment:
Last Closed: 2015-08-24 07:10:09 UTC
Embargoed:


Attachments (Terms of Use)

Description RajeshReddy 2015-06-08 08:57:32 UTC
Description of problem:
=========================
Good to use same "scrub-frequency" value across commands


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


How reproducible:


Steps to Reproduce:
1.While setting the scrubber frequency we are using scrub-frequency but where as while resetting the scrubber frequency we are using scrub-freq and value should be same across all commands 
2.

3.

Actual results:


Expected results:


Additional info:

Comment 5 Gaurav Kumar Garg 2015-08-12 06:51:45 UTC
upstream patch already available for this bug:  http://review.gluster.org/#/c/11888/

Comment 6 Gaurav Kumar Garg 2015-08-24 07:10:09 UTC
This is not actually a bug. As we are using command #gluster volume bitrot <VOLNAME> scrub-frequency <scrub frequency value>   to set option scrub-freq. Here we are not using gluster volume set framework to set the option value. Here we are using command which is having different handler to set "scrub-freq" option value. 

Command #gluster volume info <VOLNAME> also displaying the same option scrub-freq and its value. So during volume reset we are going to use the same option key that is displaying in gluster volume info command so current behaviour is correct only. This is not a bug, closing this bug.

Comment 7 Gaurav Kumar Garg 2015-08-25 06:46:36 UTC
Decision of closing this bug came after discussing and consensus with team and QA rajesh reddy. Feel free to change the status of this bug if you will have any doubt in future.


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