Skip to content

Api - importVm not check mem/cpu #11868

@tanganellilore

Description

@tanganellilore

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions