XCP-NG VM/Kubernetes node dynamic scale failed.

##### ISSUE TYPE

* Bug Report

##### COMPONENT NAME

~~~
UI
~~~

##### CLOUDSTACK VERSION

~~~
4.18.0 and 4.18.1
~~~

##### CONFIGURATION

##### OS / ENVIRONMENT

XCP-NG 8.2.1

Current setup:
cpu.overprovisioning.factor = 2
mem.overprovisioning.factor = 2

same result with:
cpu.overprovisioning.factor = 1
mem.overprovisioning.factor = 1

test VM 1 CPU x 0.50 Ghz and 512 MB memory


##### SUMMARY

Unable to dynamic scale VM from different templates (Debian, Ubuntu, Centos)

GUI error:
Unhandled exception

Log error:
2023-12-08 04:13:57,203 ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-27:ctx-ff0ece9e job-1340/job-13
42 ctx-23ed9399) (logid:15e9aadd) Invocation exception, caused by: com.cloud.utils.exception.CloudRuntimeExcep
tion: Unable to scale vm due to Catch exception com.cloud.utils.exception.CloudRuntimeException when scaling V
M:i-8-254-VM due to com.cloud.utils.exception.CloudRuntimeException: Cannot scale up the vm because of memory
constraint violation: 0 <= memory-static-min(268435456) <= memory-dynamic-min(2147483648) <= memory-dynamic-ma
x(4294967296) <= memory-static-max(536870912)

Cannot scale up the vm because of memory constraint violation: 0 <= memory-static-min(268435456) <= memory-d
ynamic-min(2147483648) <= memory-dynamic-max(4294967296) <= memory-static-max(536870912)
at com.cloud.vm.VirtualMachineManagerImpl.orchestrateReConfigureVm(VirtualMachineManagerImpl.java:4648
)
at com.cloud.vm.VirtualMachineManagerImpl.reConfigureVm(VirtualMachineManagerImpl.java:4579)
at com.cloud.vm.VirtualMachineManagerImpl.orchestrateReconfigure(VirtualMachineManagerImpl.java:5522)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5536)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.ja
va:620)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:
55)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedCont
ext.java:102)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedConte
xt.java:52)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)

##### STEPS TO REPRODUCE

~~~
Create VM with 1 or more CPUs and select dynamic scalable in VM, Template, Global properties.
Try to scale running VM.
~~~

##### EXPECTED RESULTS

~~~
VM scaled successfully
~~~

##### ACTUAL RESULTS

~~~
VM scale failed result
~~~

Beginne mit den Reproduktionsschritten und der XCP-NG-Umgebung und untersuche anschließend VirtualMachineManagerImpl.java bei orchestrateReConfigureVm (Zeile 4648), reConfigureVm und orchestrateReconfigure unter Verwendung der gemeldeten Memory-Constraint-Exception. Reproduziere die fehlgeschlagene dynamische Skalierungsoperation und verfolge die Größenwerte; abgeschlossen ist die Aufgabe, wenn die VM über alle aufgeführten Templates und Konfigurationen hinweg erfolgreich skaliert wird.

Vom Indexierungsmodell aus dem Issue-Text verfasst.