Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1499746 - Hpa v1 fail to get metrics
Hpa v1 fail to get metrics
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity high
: ---
: 3.7.0
Assigned To: Solly Ross
xiuli
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-09 06:20 EDT by xiuli
Modified: 2017-11-28 17:15 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:15:54 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)
Description xiuli 2017-10-09 06:20:51 EDT
Description of problem:
Fail to get Metrics, and can not auto scale

Version-Release number of selected component (if applicable):
3.7.0


Steps to Reproduce:
1: oc new-project sszr1 
2: oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/hpa/rc-hello-openshift.yaml
3: oc autoscale rc/hello-openshift --min=2 --max=10
4: oc get hpa

The actual result:
NAME              REFERENCE                               TARGETS           MINPODS   MAXPODS   REPLICAS   AGE
hello-openshift   ReplicationController/hello-openshift   <unknown> / 80%   2         10        0          1m

The expected result: the target value should be some digital value, not "unknown" 

5: if check the number of pod "oc describe replicationcontrollers hello-openshift", will show only 1 pod, the expected value should be at least 2.

Addition info: found the following log in master:
 Oct  9 06:15:25 ip-172-18-10-208 atomic-openshift-master-controllers: E1009 10:15:25.022268   13121 horizontal.go:206] failed to query scale subresource for ReplicationController/dma/hello-openshift: User "system:serviceaccount:openshift-infra:horizontal-pod-autoscaler" cannot get replicationcontrollers.extensions/scale in the namespace "dma": User "system:serviceaccount:openshift-infra:horizontal-pod-a
<deshuai> <deshuai> utoscaler" cannot get replicationcontrollers/scale.extensions in project "dma" (get replicationcontrollers.extensions hello-openshift)
Comment 1 DeShuai Ma 2017-10-09 21:44:08 EDT
openshift v3.7.0-0.143.1
kubernetes v1.7.0+80709908fd
etcd 3.2.1
Comment 2 Solly Ross 2017-10-18 09:21:12 EDT
Already fixed in Origin https://github.com/openshift/origin/pull/16711.
Comment 3 xiuli 2017-10-23 03:49:23 EDT
Verified the bug and it can not be reproduced on the environment: openshift v3.7.0-0.143.7 + kubernetes v1.7.0+80709908fd + etcd 3.2.1, @sross@redhat.com, could you please set the bug as on_qe status.
Comment 7 errata-xmlrpc 2017-11-28 17:15:54 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.