Michael created CLOUDSTACK-3423:
-----------------------------------
Summary: The allocated VM usage doesn't reflect changes to the
Service Offering
Key: CLOUDSTACK-3423
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3423
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Usage
Affects Versions: 4.1.0
Reporter: Michael
Service offering changes on a stopped VM are not reflected in the allocated VM
usage records:
Case 1:
- Create VM with Service Offering A
- Stop this VM
- Change VM's Service Offering A --> Service Offering B in the UI
- Leave VM stopped
The Allocated usage for the VM in the above case will still be generated with
Service Offering A. There is no VM.DESTROY, VM.CREATE, or VM.UPGRADE usage
event created to indicate that the allocated VM now has a different service
offering.
This piece is critical so that we can properly bill a customer for their
allocated VM that has changed their service offering.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
