Bug 1493347 - Wrong HPA condition - ScalingLimited while CPU usage is zero
Summary: Wrong HPA condition - ScalingLimited while CPU usage is zero
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.7.0
Assignee: Solly Ross
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-20 02:31 UTC by Zhang Cheng
Modified: 2017-11-28 22:11 UTC (History)
6 users (show)

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.
Clone Of:
Environment:
Last Closed: 2017-11-28 22:11:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

Comment 1 Seth Jennings 2017-09-20 04:30:30 UTC 
Solly, PTAL with you have a chance.
Comment 2 Solly Ross 2017-09-21 18:51:45 UTC 
Yep, there's a fix submitted upstream on the linked issue (https://github.com/kubernetes/kubernetes/pull/52168).
Comment 3 Seth Jennings 2017-10-03 19:09:42 UTC 
Origin PR:
https://github.com/openshift/origin/pull/16664
Comment 4 Seth Jennings 2017-10-10 01:35:52 UTC 
oops
Comment 5 xiuli 2017-10-23 10:05:54 UTC 
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?
Comment 6 Seth Jennings 2017-10-23 14:02:19 UTC 
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.
Comment 7 DeShuai Ma 2017-10-24 02:24:53 UTC 
As comment5 move to verified
Comment 11 errata-xmlrpc 2017-11-28 22:11:25 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.