You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Harikrishna Patnala (JIRA)" <ji...@apache.org> on 2014/04/21 12:23:15 UTC

[jira] [Updated] (CLOUDSTACK-6466) cpu and ram is not getting updated correctly in usage_vm_instance table for usage type 2

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harikrishna Patnala updated CLOUDSTACK-6466:
--------------------------------------------

    Status: Reviewable  (was: In Progress)

> cpu and ram is not getting updated correctly in usage_vm_instance table for usage type 2
> ----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6466
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6466
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.4.0
>            Reporter: Harikrishna Patnala
>            Assignee: Harikrishna Patnala
>             Fix For: 4.4.0
>
>
> steps to reproduce
> ==================
> 1-prepare a cs setup with xen server
> 2-create a dynamic compute offering
> 3-deploy a vm with dynamic compute offerings(cpu=500,ram=513
> 4- scale the vm to regular compute offerings(cpu=1000 ram=1024)
> 5- check the usage_vm_instance table in usage db
> expected:
> =========
> value of cpu and ram should be same for resource usage_type 1 and 2.
> Actual:
> =======
> cpu and ram set to null for usage_type 1 , but usage_type 2 is holding the old value(before scaling up)
> DB
> ===
>  mysql> select * from usage_vm_instance where vm_instance_id=10;
> +------------+---------+------------+----------------+---------+---------------------+-------------+-----------------+---------------------+---------------------+-----------+-----------+--------+
> | usage_type | zone_id | account_id | vm_instance_id | vm_name | service_offering_id | template_id | hypervisor_type | start_date          | end_date            | cpu_speed | cpu_cores | memory |
> +------------+---------+------------+----------------+---------+---------------------+-------------+-----------------+---------------------+---------------------+-----------+-----------+--------+
> |          1 |       1 |          2 |             10 | USG4    |                  13 |           5 | XenServer       | 2014-02-24 17:13:11 | 2014-02-24 17:13:33 |       300 |         1 |    512 |
> |          1 |       1 |          2 |             10 | USG4    |                   2 |           5 | XenServer       | 2014-02-24 17:13:33 | NULL                |      NULL |      NULL |   NULL |
> |          2 |       1 |          2 |             10 | USG4    |                  13 |           5 | XenServer       | 2014-02-24 17:12:38 | 2014-02-24 17:13:33 |       300 |         1 |    512 |
> |          2 |       1 |          2 |             10 | USG4    |                   2 |           5 | XenServer       | 2014-02-24 17:13:33 | NULL                |       300 |         1 |    512 |
> +------------+---------+------------+----------------+---------+---------------------+-------------+-----------------+---------------------+---------------------+-----------+-----------+--------+
> 4 rows in set (0.00 sec)



--
This message was sent by Atlassian JIRA
(v6.2#6252)