Bug 1493347
| Summary: | Wrong HPA condition - ScalingLimited while CPU usage is zero | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Zhang Cheng <chezhang> |
| Component: | Node | Assignee: | Solly Ross <sross> |
| Status: | CLOSED ERRATA | QA Contact: | DeShuai Ma <dma> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.7.0 | CC: | aos-bugs, dma, jokerman, mmccomas, sjenning, xiuli |
| Target Milestone: | --- | ||
| Target Release: | 3.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
The descriptive text on the Horizontal Pod Autoscaler's ScalingLimited now has more descriptive text when a minimum replica count is set and the desired replica count would be zero.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-11-28 22:11:25 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: | |||
|
Comment 1
Seth Jennings
2017-09-20 04:30:30 UTC
Yep, there's a fix submitted upstream on the linked issue (https://github.com/kubernetes/kubernetes/pull/52168). oops Tested the bug on the env openshift v3.7.0-0.158.0 + kubernetes v1.7.6+a08f5eeb62 + etcd 3.2.8, and the status message is shown as "the desired replica count was zero" which is more informative. @Seth, could you please move the bug to on_qa? Typically is it the job of a QE person (or maybe a bot) to move from modified to on_qa once the change is included in a build. However, you just verified the fix. I'll let DeShuai move this along. 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/RHSA-2017:3188 |