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:
Fix provided in: https://github.com/kubernetes/kubernetes/pull/27844
Upstream PR has merged.
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?
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
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