[
https://issues.apache.org/jira/browse/CLOUDSTACK-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630880#comment-14630880
]
ASF GitHub Bot commented on CLOUDSTACK-8602:
--------------------------------------------
Github user sateesh-chodapuneedi commented on the pull request:
https://github.com/apache/cloudstack/pull/548#issuecomment-122199556
LGTM.
I see this patch is updating chain information for all 3 cases of storage
migration,
1) volume migration
2) vm migration with storage within cluster
3) vm migration across storage within cluster
> 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)
