You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kishan Kavala (JIRA)" <ji...@apache.org> on 2013/06/27 12:30:20 UTC
[jira] [Created] (CLOUDSTACK-3231) Allocated Vm usage doesn't
reflect the Service Offering changes
Kishan Kavala created CLOUDSTACK-3231:
-----------------------------------------
Summary: Allocated Vm usage doesn't reflect the Service Offering changes
Key: CLOUDSTACK-3231
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3231
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Usage
Reporter: Kishan Kavala
Assignee: Kishan Kavala
Fix For: 4.2.0
Service offering changes on a VM ( Stopped VM) are not reflected in the allocated VM usage.
Following is the scenario,
case 1:
- create VM with Service Offering A
- stop this VM
- change VM's Service Offering A --> Service Offering B
- leave VM stopped
The Allocated usage for the VM in the above case will still be generated with Service Offering A.
case 2:
- create VM with Service Offering A
- stop this VM
- change VM Service Offering A --> Service Offering B
- Reboot VM
.
In the above case the Allocated VM usage also reflects the service offering as "Service Offering A" , But running VM usage reflects the service offering as "Service Offering B".
--
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