Bug 1005465

Summary: quota: setting the soft/hard-timeout are reported in logs not on stdout
Product: Red Hat Gluster Storage Reporter: Saurabh <saujain>
Component: glusterdAssignee: Krutika Dhananjay <kdhananj>
Status: CLOSED ERRATA QA Contact: Saurabh <saujain>
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: amarts, asriram, kaushal, kparthas, mzywusko, rhs-bugs, shaines, vbellur
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.4.0.34rhs Doc Type: Bug Fix
Doc Text:
Previously, quota options such as 'default-soft-limit', 'hard-timeout', 'soft-timeout' and 'alert-time' were not validated by glusterd. This resulted in invalid values in the brick volfile and restarting bricks failed due to validation failure of the option's value. Now with this update, glusterd validates the values and rejects any values falling out of range. It also reports the allowed range of values to the CLI.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-27 15:36:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
sosreport of a node none

Description Saurabh 2013-09-07 10:19:51 UTC 
Description of problem:
response for setting soft/hard timeout should turn out to be an error for cli.

Version-Release number of selected component (if applicable):
glusterfs-3.4.0.32rhs-1.el6rhs.x86_64

How reproducible:
always

Steps to Reproduce:
1. enable quota on a volume
2. set quota soft-timeout hard-timeout to 100hr
3.

Actual results:
the result is reported ad error in logs but the command it self is a pass.

[2013-09-07 10:10:16.370916] E [options.c:443:xlator_option_validate_time] 0-newvol-quota: '360000' in 'option soft-timeout 100hr' is out of range [0 - 1800]
[2013-09-07 10:10:16.372660] E [options.c:443:xlator_option_validate_time] 0-newvol-quota: '360000' in 'option soft-timeout 100hr' is out of range [0 - 1800]


Expected results:
the stdout should also send a response about the range and should not let such a big number to be set.

Additional info:
Comment 2 Saurabh 2013-09-07 10:23:29 UTC 
Created attachment 795086 [details]
sosreport of a node
Comment 6 errata-xmlrpc 2013-11-27 15:36:59 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.

http://rhn.redhat.com/errata/RHBA-2013-1769.html