Bug 975707 - rhc would hang up if using "0" or negative numbers as the limit value
Summary: rhc would hang up if using "0" or negative numbers as the limit value
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: oc
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: N. Harrison Ripps
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-19 07:53 UTC by joycezhang
Modified: 2015-05-15 02:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-24 14:57:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description joycezhang 2013-06-19 07:53:18 UTC
Description of problem:
If trying to use invalid value like "0" or negative numbers as the limit value, rhc commmand would hang up.



Version-Release number of selected component (if applicable):
INT(devenv_3382)
rhc-1.10.3.gem

How reproducible:
always

Steps to Reproduce:
1.Create a scalable app and add some cartridges to the app.
2.rhc ssh app --gears ls --limit -1/0


Actual results:
rhc command hang up and no response.

Expected results:
Invalid argument error is shown.

Additional info:

Comment 1 N. Harrison Ripps 2013-06-19 14:50:26 UTC
Assigned

Comment 2 joycezhang 2013-06-20 06:47:33 UTC
Checked this bug has been fixed with rhc-1.10.4 as below:

# rhc ssh py26s --gears ls --limit -1
--limit must be an integer greater than zero
Usage: rhc ssh <app> [--ssh path_to_ssh_executable]
Pass '--help' to see the full list of options
[root@joycezh errata-rails]# rhc ssh py26s --gears ls --limit 0
--limit must be an integer greater than zero
Usage: rhc ssh <app> [--ssh path_to_ssh_executable]
Pass '--help' to see the full list of options

Message "--limit must be an integer greater than zero" is shown resonably. So this bug can be moved to "verified" once it's on_qa. Thanks.

Comment 3 Wei Sun 2013-06-21 00:28:15 UTC
According to #Comment 2,move this bug to VERIFIED status.


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