This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 987280 - The min number of gears can be set to be bigger than max number.
The min number of gears can be set to be bigger than max number.
Product: OpenShift Online
Classification: Red Hat
Component: Pod (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Abhishek Gupta
libra bugs
: Regression
Depends On:
  Show dependency treegraph
Reported: 2013-07-23 03:15 EDT by Yujie Zhang
Modified: 2015-05-14 20:19 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-07 18:55:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Yujie Zhang 2013-07-23 03:15:44 EDT
Description of problem:

Set 2 to be minmum gear numbers of app and 1 to be maxmum gear number, and it can be saved, it should not allow to set min number bigger than max number.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Set 2 to be minmum gear number of app from website
2.Set 1 to be maxmum gear number of app from website
3.Click the "Save" button

Actual results:

It can be saved successfully, and restapi result like the following:


Expected results:

It should not allow to set min gear number bigger than max gear number.

Additional info:
Comment 1 Abhishek Gupta 2013-07-23 14:46:14 EDT
Could not reproduce on the latest devenv. The UI automatically switches the min and max values assuming it to be a user input error. If the REST API call is made with the invalid values, an error message is returned.
Comment 2 Yujie Zhang 2013-07-23 23:36:07 EDT
Tested on devenv_3544, can not reproduce this issue, UI will switch the min and max when they are invalid, so verify this bug, thanks.

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