cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8745) After a volume is migrated; the usage table still shows the old volume id
Date Mon, 25 Apr 2016 19:53:12 GMT

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

ASF subversion and git services commented on CLOUDSTACK-8745:
-------------------------------------------------------------

Commit a2d46921a1ad8851da0c5060443e59673df78489 in cloudstack's branch refs/heads/master from
[~williamstevens@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a2d4692 ]

Merge pull request #713 from nitt10prashant/pool_maint

CLOUDSTACK-8745 : verify usage after root disk migrationput 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

* pr/713:
  CLOUDSTACK-8745 : verify usage after root disk migration

Signed-off-by: Will Stevens <williamstevens@gmail.com>


> 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)

Mime
View raw message