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 2015/08/09 21:15:46 UTC
[jira] [Commented] (CLOUDSTACK-8602)
MigrateVirtualMachineWithVolume leaves old chain data for volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679285#comment-14679285 ]
ASF GitHub Bot commented on CLOUDSTACK-8602:
--------------------------------------------
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/548#issuecomment-129227023
Who wants to step in and finish this work? It seems the original author is not able to finish it. If no one steps in, we'll have to close the PR without merging it so please help :-).
> MigrateVirtualMachineWithVolume leaves old chain data for volume
> ----------------------------------------------------------------
>
> Key: CLOUDSTACK-8602
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8602
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Fix For: 4.6.0
>
>
> CS maintains chain info of every volume in DB, where chain info is the complete volume path. When the volumes associated with a VM are migrated to different storage pool, their chain info changes, but this information is not reflected in the DB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)