Bug 1336632 – hpa wrong tips when --max is less than --min

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1336632 - hpa wrong tips when --max is less than --min

Summary:	hpa wrong tips when --max is less than --min

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Pod (Show other bugs)
Sub Component:
Version:	3.4.0
Hardware:	Unspecified Unspecified

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	dhodovsk
QA Contact:	DeShuai Ma
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-05-17 01:57 EDT by Weihua Meng
Modified:	2017-03-08 13 EST (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	While autoscaling, it was not clear what was the reason of failed --max flag validation. This fix divides reasons to: - value not provided or too low - value of max is lower than value of min
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-01-18 07:40:53 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:0066	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.4 RPM Release Advisory	2017-01-18 12:23:26 EST

Groups: None (edit)

Description Weihua Meng 2016-05-17 01:57:30 EDT

Description of problem:
Wrong tips show up when --max is less than --min for oc autoscale

Version-Release number of selected component (if applicable):
oc v3.2.0.44
kubernetes v1.2.0-36-g4a3f9c5


How reproducible:
Always

Steps to Reproduce:
1. create RC
2. oc autoscale rc $rcName --max=5 --min=6

Actual results:
--max=MAXPODS is required, and must be at least 1 and --min=MINPODS

Expected results:
something point out the reason, like
--max=MAXPODS must be larger or equal to --min=MINPODS

Additional info:

Comment 1 dhodovsk 2016-06-22 04:27:39 EDT

Fix provided in: 
https://github.com/kubernetes/kubernetes/pull/27844

Comment 2 Andy Goldstein 2016-07-06 11:44:35 EDT

Upstream PR has merged.

Comment 3 Weihua Meng 2016-07-14 04:04:14 EDT

oc autoscale rc $rcName --max=5 --min=6
--max=MAXPODS is required, and must be at least 1 and --min=MINPODS
[root@openshift-140 ~]# openshift version
openshift v3.3.0.5
kubernetes v1.3.0+57fb9ac
etcd 2.3.0+git

need to wait.
which openshift version to verify it?

Comment 4 DeShuai Ma 2016-11-22 03:40:44 EST

Test on openshift v3.4.0.28+dfe3a66, This bug should be fixed in 3.4, could you set on QA, then QE will verify it.

[root@qe-dma2-master-1 dma]# oc autoscale rc hello-openshift --max=5 --min=6 -n dma2
error: --max=MAXPODS must be larger or equal to --min=MINPODS, max: 5, min: 6

Comment 6 errata-xmlrpc 2017-01-18 07:40:53 EST

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:0066

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