Bug 1828731 - For autoscaling from zero the autoscaler should convert the mem value consistently with other providers
Summary: For autoscaling from zero the autoscaler should convert the mem value consist...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Alberto
QA Contact: sunzhaohua
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-28 09:22 UTC by Alberto
Modified: 2020-07-13 17:32 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:32:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kubernetes-autoscaler pull 146 0 None closed Bug 1828731: UPSTREAM: <carry>: Convert the mem value consistently with other providers 2021-01-27 06:48:32 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:32:18 UTC

Description Alberto 2020-04-28 09:22:57 UTC
Description of problem:
For autoscaling from zero, the autoscaler should convert the mem value received in the appropriate annotation to bytes using powers of two consistently with other providers and fail if the format received is not expected. This gives robust behaviour consistent with cloud providers APIs and providers implementations.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 sunzhaohua 2020-05-19 09:46:03 UTC
Verified

clusterversion: 4.5.0-0.nightly-2020-05-17-220731
aws m4.large 
    machine.openshift.io/GPU: "0"
    machine.openshift.io/memoryMb: "8192"
    machine.openshift.io/vCPU: "2"
aws a1.2xlarge 
    machine.openshift.io/GPU: "0"
    machine.openshift.io/memoryMb: "16384"
    machine.openshift.io/vCPU: "8"

azure Standard_D2s_v3
    machine.openshift.io/GPU: "0"
    machine.openshift.io/memoryMb: "8192"
    machine.openshift.io/vCPU: "2"

azure Standard_D3_v2
    machine.openshift.io/GPU: "0"
    machine.openshift.io/memoryMb: "14336"
    machine.openshift.io/vCPU: "4"

gcp n1-standard-2:
    machine.openshift.io/memoryMb: "7680"
    machine.openshift.io/vCPU: "2"

gcp n1-standard-4:
    machine.openshift.io/memoryMb: "15360"
    machine.openshift.io/vCPU: "4"

Comment 4 errata-xmlrpc 2020-07-13 17:32:07 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/RHBA-2020:2409


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