We are setting different capacities for one EC2 host in ONE. For example, M1_SMALL with value 3, T2_SMALL with value 1… The problem is when we instantiate several VMs. So when we try to start 4 m1.small they boot and turn on although the limit is set to 3 in that host. We only have one host and no priority or anything like that set. We have also checked the DB and those values are correctly saved although it seems that ONE ignores them completely.
Versions of the related components and OS (frontend, hypervisors, VMs):
CentOS 7 with OpenNebula 5.4.5.
Steps to reproduce:
Create an EC2 host and set capacity for M1_SMALL with value 3. Then, start 4 VMs on that host with type m1.small.
4 VMs running.
3 VMs running.