Description of problem: ======================= Gluster CLI option "--timeout" is accepting non numeric and negative values. This option is introduced for the issue: https://bugzilla.redhat.com/show_bug.cgi?id=1340338 Non Numeric value setting [root@ ~]# gluster --timeout=xvafgs volume status replica inode ^Z [1]+ Stopped gluster --timeout=xvafgs volume status replica inode [root@ ~]# Negative value setting: ~]# gluster --timeout=-12 volume status replica inode ^Z [2]+ Stopped gluster --timeout=-12 volume status replica inode [root@ ~]# Version-Release number of selected component (if applicable): =========================================================== glusterfs-3.8.4-2 How reproducible: ================= Always Steps to Reproduce: 1. Use CLI option "--timeout=" with negative values and non numeric values. 2. 3. Actual results: =============== CLI option "--timeout" is accepting negative and non numeric values Expected results: ================ It should accept only positive numeric values Additional info:
upstream patch : https://review.gluster.org/16578
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101312/
Verified in the build: glusterfs-3.8.4-21 CLI option --timeout is accepting only positive integers throws correct error message when non-numeric and negative integers are given [root@dhcp37-135 /]# gluster vol status testvol inode --timeout=ab timeout value should be a postive integer [root@dhcp37-135 /]# gluster vol status testvol inode --timeout=1ab timeout value should be a postive integer [root@dhcp37-135 /]# gluster vol status testvol inode --timeout=10ab timeout value should be a postive integer [root@dhcp37-135 /]# gluster vol status testvol inode --timeout=10! timeout value should be a postive integer [root@dhcp37-135 /]# gluster vol status testvol inode --timeout=10~ timeout value should be a postive integer [root@dhcp37-135 /]# gluster vol status testvol inode --timeout=-10 timeout value should be a postive integer Hence marking the bug verified
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. https://access.redhat.com/errata/RHBA-2017:2774