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:
Created attachment 795086 [details] sosreport of a node
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