Version: $ openshift-install version all Platform: ovirt/rhv Please specify: all What happened? 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. I don't think the nodes/vms running overcommiting the memory is very recommended and it can cause the nodes been unstable (specially in the installation, making it fail because takes longer than 30/20 min) What did you expect to happen? guarantee memory set according with user input memory How to reproduce it (as minimally and precisely as possible)? Anything else we need to know? there is a ovirt/rhv RFE for it on rhv side: https://bugzilla.redhat.com/show_bug.cgi?id=1940529
Thanks Gui! Douglas added you because it sounds like a fun fix on the installer ** Maybe terraform provider as well Plus need to check that this is not happening on new machines, if that is the case then cluster-api-provider should be patched as well on a separate bug, Gui can you check that and open a new bug if needed?
On new machines do you mean like when we scale up and down the cluster? If that is the case, yes. it does happen on new machines
due to capacity constraints we will be revisiting this bug in the upcoming sprint
@gal- sure I'm working on it. adding support for guranateed_memory for the terraform provider: https://github.com/oVirt/terraform-provider-ovirt/pull/271
masters and workers are using the same rhcos template, so making this configuration part of the RHV template is problematic. we can override the template configuration in VM level (same as setting the VM Memory)
need to implement in the VM level. moving back to assigned
Closing this since it is not needed any more, the guaranteed memory issue only occurs in RHV 4.4.7 and we added a field to the machine object to be able to set it as a day2 op. There is a KCS that explains all the changes across the RHV versions https://access.redhat.com/articles/6454811. Please reopen if there is a need