CPU and memory values modified by the Service Provider do not reflect in vCloud Director

Products

• VMware

Issue/Introduction

Symptoms:
When you change resource values during a vApp deployment in vCloud Director, you experience these symptoms:

• Modified CPU, memory, or storage values are not reflecting in Audit_Event.
• The deployed virtual machine has incorrect resource usages in vCenter Chargeback. This leads to incorrect charges in the cost report.
  

Cause

If you change the CPU, memory, or storage values for the virtual machine during the vApp deployment, the virtual machine is deployed with the changes but do not reflect changes in the vm_create event stored in the Audit_Event table in vCloud Director. The vm_create event for the deployed virtual machine has the original CPU, memory, and storage values configured in the template.

vCenter Chargeback uses vm_create events from the Audit_Event table for calculating the virtual machines resource usages in the cost report. When you change the value from the Wizard during the vApp deployment, it leads to incorrect charges in the cost report.

Resolution

This issue is resolved in VMware vCloud Director 8.0.1, available at VMware Downloads.