[CLOUDSTACK-9338] updateResourceCount not accounting resources of VMs with custom service offering

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.5.2, 4.8.0
• Fix Version/s: 4.12
• Component/s: API, Cloudmonkey, UI
• Security Level: Public (Anyone can view this level - this is the default.)
• Environment: CloudStack 4.5.1; MariaDB 10.0 and 10.1
• Assignee: Rafael Weingärtner
• Reporter: Francois Scheurer
• Created: 05/Apr/16 13:17
• Updated: 09/May/18 10:00
• Resolved: 23/Feb/18 14:08

Description

listAccount on a domain returns 0 for cputotal and memorytotal if the domain accounts own VMs using a ComputeOffering with custom=enabled.

Basically, looking into the vm_instance table you get the service_offering_id and in the service_offering table you find normally the amount of CPU/RAM allocated for the VM.

But if your VM's ComputeOffering has custom=enabled, then you need to get the specific CPU/RAM values from the user_vm_details table:
mysql> select * from user_vm_details WHERE vm_id=957;

Apparently the listAccount code is not doing that and it just returns zero, because the service_offering table has cpu=0 and ram_size=0 for ComputeOfferings with custom=enabled.

solution: the SQL query of listAccount should also look in the user_vm_details table for matching rows. (instead of just querying in the service_offering table)

Issue Links

• links to: GitHub Pull Request #2443