Bug 1031683 - Gluster volume set "least-rate-limit" command returning success for invalid arguments
Summary: Gluster volume set "least-rate-limit" command returning success for invalid a...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Lalatendu Mohanty
URL:
Whiteboard: glusterd
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 14:37 UTC by Lalatendu Mohanty
Modified: 2015-03-23 07:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Lalatendu Mohanty 2013-11-18 14:37:18 UTC 
Description of problem:

Gluster volume set "least-rate-limit" command returning return code 0 (i.e. success) for wrong inputs.

gluster volume set <Volume> least-rate-limit -2 

Expected 1-255, got 0

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

How reproducible:
Always

Steps to Reproduce:
1. Create a gluster volume
2. Run "gluster volume set <Volume> least-rate-limit -2 
3. echo $?

Actual results:

it return 0

Expected results:

it should be Non zero

Additional info:

This bug is not present in RHS2.1
Comment 2 Vivek Agarwal 2015-03-23 07:39:05 UTC 
The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) [1], hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version.







[1] https://rhn.redhat.com/errata/RHSA-2014-0821.html
Comment 3 Vivek Agarwal 2015-03-23 07:40:07 UTC 
The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) [1], hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version.







[1] https://rhn.redhat.com/errata/RHSA-2014-0821.html
Note You need to log in before you can comment on or make changes to this bug.