[
https://issues.apache.org/jira/browse/CLOUDSTACK-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499865#comment-14499865
]
ASF subversion and git services commented on CLOUDSTACK-8319:
-------------------------------------------------------------
Commit 55f2e45d14fe08fc88540616b7b3720fe12f5d4b in cloudstack's branch
refs/heads/4.5 from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=55f2e45 ]
CLOUDSTACK-8319. For both 'MigrateVolume' and 'MigrateVMWithVolumes, ensure
VM's vconfiguration files are migrated along with VM's root volume.
(cherry picked from commit bdd28a45ed1cc8046c63d0e840e54975e5b74ab5)
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> [VMware] VM's configuration files are left behind on source primary storage
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8319
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8319
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: 4.6.0
>
>
> In case of VMware, during VM or volume migration, VM's configuration files
> (for e.g. .VMX file) are left behind on the source primary storage. This
> makes it very difficult to retire a primary storage.
> Instead we need to ensure that VM's configuration files are migrated along
> with VM's root volume during a live migration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
