Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1493347 - Wrong HPA condition - ScalingLimited while CPU usage is zero
Wrong HPA condition - ScalingLimited while CPU usage is zero
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.7.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.7.0
Assigned To: Solly Ross
DeShuai Ma
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-19 22:31 EDT by Zhang Cheng
Modified: 2017-11-28 17:11 EST (History)
6 users (show)

See Also:
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 17:11:25 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Comment 1 Seth Jennings 2017-09-20 00:30:30 EDT
Solly, PTAL with you have a chance.
Comment 2 Solly Ross 2017-09-21 14:51:45 EDT
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 15:09:42 EDT
Origin PR:
https://github.com/openshift/origin/pull/16664
Comment 4 Seth Jennings 2017-10-09 21:35:52 EDT
oops
Comment 5 xiuli 2017-10-23 06:05:54 EDT
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 10:02:19 EDT
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-23 22:24:53 EDT
As comment5 move to verified
Comment 11 errata-xmlrpc 2017-11-28 17:11:25 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/RHSA-2017:3188

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