You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/22 08:17:12 UTC
[jira] [Commented] (CLOUDSTACK-8745) After a volume is migrated;
the usage table still shows the old volume id
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253430#comment-15253430 ]
ASF GitHub Bot commented on CLOUDSTACK-8745:
--------------------------------------------
Github user nitt10prashant commented on the pull request:
https://github.com/apache/cloudstack/pull/713#issuecomment-213278268
@bhaisaab rebased and merged into single commit ,@swill @koushik-das can you please look into this
> 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)