[jira] [Commented] (CLOUDSTACK-8745) After a volume is migrated; the usage table still shows the old volume id

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701102#comment-14701102 ] 

ASF GitHub Bot commented on CLOUDSTACK-8745:
--------------------------------------------

GitHub user nitt10prashant opened a pull request:

    https://github.com/apache/cloudstack/pull/713

    CLOUDSTACK-8745 : verify usage after root disk migration

    put storage in maintenance mode and start ha vm and check usage ... === TestName: test_ha_with_storage_maintenance | Status : SUCCESS ===
    ok
    
    ----------------------------------------------------------------------
    Ran 1 test in 842.294s
    
    OK

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nitt10prashant/cloudstack pool_maint

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/713.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #713
    
----
commit d276a3579f7f055b5431575a5bb498d96dfc9f45
Author: nitt10prashant <ni...@gmail.com>
Date:   2015-08-18T11:23:54Z

    CLOUDSTACK-8745 : verify usage after root disk migration

----


> After a volume is migrated; the usage table still shows the old volume id
> -------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8745
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8745
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: marvin, Usage
>    Affects Versions: 4.5.0
>            Reporter: prashant kumar mishra
>            Assignee: prashant kumar mishra
>
> After a volume is migrated; the usage table still shows the old volume id
> steps to verify:
> ==========
> 1-Created a HA VM with both root and data disk
> 2. Add one more primary storage to this cluster
> 3. Put the original /old Primary storage into maintenance which has the root and data disk of VM created in step 1
> 4. Start the VM which was stopped as a part of step 3
> 5. Check for VOLUME.DELETE & VOLUME.CREATE events for root disk and data disk in usage_event table



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)