[
https://issues.apache.org/jira/browse/CLOUDSTACK-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712848#comment-14712848
]
ASF subversion and git services commented on CLOUDSTACK-8602:
-------------------------------------------------------------
Commit f499281625f54ceb00aa44c3b499ad7f90d1db44 in cloudstack's branch
refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f499281 ]
CLOUDSTACK-8602. MigrateVirtualMachineWithVolume leaves old chain data for
volume. Update chain info of a volume after migration.
Signed-off-by: Rohit Yadav <[email protected]>
This closes #548
> 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: Suresh Kumar Anaparti
> 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)
