[
https://issues.apache.org/jira/browse/CLOUDSTACK-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358202#comment-14358202
]
Rohit Yadav commented on CLOUDSTACK-8319:
-----------------------------------------
[~likithas] should the fix for this go into 4.5 branch?
> [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)
