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:
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"
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