Skip to content

Compute resources are not automatically released after vm stop #3482

@div8cn

Description

@div8cn
ISSUE TYPE
  • Improvement Request
COMPONENT NAME
Management Server
Usage Server
CLOUDSTACK VERSION
4.9/4.11/4.11.2/4.11.3
CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

The computing resource cannot be released after the VM is stopped. You must execute delete to release the computing resource.

After the VM is stopped, it does not consume any computing resources. We should not think that it still occupies computing resource quota (aws azure google cloud is designed in this way).

STEPS TO REPRODUCE
1. Create an account and update the following resource quotas
    Instance Limits=5
    CPU limits=8
    Memory limits (MiB)=32G
2. Create and run two VMs under the new account:
    Name=vm1,vcpu=4,ram=16
    Name=vm2,vcpu-4,ram=16

3. Stoped vm1, vm2

4. Create a third VM under account (test1)
    Name=vm3,vcpu=4,ram=16 
EXPECTED RESULTS
vm3 can be successfully created and run
ACTUAL RESULTS
Error:
Maximum amount of resources of Type = 'cpu' for Account Name = test1 in Domain Id = 4 is exceeded: Account Resource Limit = 8, Current Account Resource Amount = 8 Requested Resource Amount = 4.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions