Bug 1336632
Summary: | hpa wrong tips when --max is less than --min | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Weihua Meng <wmeng> |
Component: | Node | Assignee: | dhodovsk |
Status: | CLOSED ERRATA | QA Contact: | DeShuai Ma <dma> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.4.0 | CC: | agoldste, aos-bugs, jokerman, mmccomas, tdawson, wmeng |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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 12:40:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Weihua Meng
2016-05-17 05:57:30 UTC
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 |