tanganellilore opened a new issue, #11868: URL: https://github.com/apache/cloudstack/issues/11868
### 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 1. import a VM via `importVm` api with custom details for mem e cpu higher than allowed cpu/mem of serviceoffering 2. start vm 3. scale resources 4. scaling go in error ### What to do about it? Introduce check in `importVm` like UI -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
