-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Milestone
Description
problem
Hi team,
i notice that if we call importVm api will not check if CPU and/or Mem is higher than serviceoffering selected.
So in case of dynamical scalable template adopted, scaling up will fail.
I don't know if this behaviour is wanted, but from UI this is not allowed.
I think that UI check should be setted also on api level.
versions
CloudStack 4.21.0.0
The steps to reproduce the bug
- import a VM via
importVmapi with custom details for mem e cpu higher than allowed cpu/mem of serviceoffering - start vm
- scale resources
- scaling go in error
What to do about it?
Introduce check in importVm like UI
gianmarco-mameli and Overmorrow1501