Description of problem: when creating nodes, openshift set the vm memory value according with the user input. However, using api/sdk, rhv/ovirt doesn't automatically set guarantee_memory based on the memory input but it gets a default value from the blanket template, which is 1Gb. Testing steps: # extract the machineset name machineset=$(oc get machinesets -n openshift-machine-api -o template --template '{{range.items}}{{.metadata.name}}{{"\n"}}{{end}}') # patch the machineset with guaranteed_memory_mb value oc patch machineset $machineset --type='merge' --patch='{"spec": { "template": { "spec": { "providerSpec": { "value": { "guaranteed_memory_mb": "16000"}}}}}}' -n openshift-machine-api # create new workers by scaling up the machineset oc scale machineset $machineset --replicas=3 -n openshift-machine-api #verify - wait for the new workers to appear at the oVirt engine - verify the new workers in oVirt engine have "Physical Memory Guaranteed" field set to new value (default is 1024MB)
High/High seems a bit excessive. @pelauter can you please review this?
verified in OpenShift cluster 4.9.0-0.nightly-2021-08-14-065522 and ovirt-engine ovirt-engine-4.4.8.2-0.11.el8ev.noarch
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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-2021:3759