[
https://issues.apache.org/jira/browse/CLOUDSTACK-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609756#comment-14609756
]
Likitha Shetty commented on CLOUDSTACK-8602:
--------------------------------------------
+Steps to reproduce+
1. Have a setup with two clusters (C1 and C2) with a host each.
2. Deploy a VM with a data volume in C1 .
3. Note down the chain info of the data volume. It can be obtained from the DB
-> table: 'volumes' ; column: 'chain_info'.
4. Use MigrateVirtualMachineWithVolume API to migrate the VM to cluster C2.
5. Compare the chain_info with the old chain_info
Observed - chain_info is not updated upon migration even though the datastore
and path of the volume changed after migration
> 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)
