You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2015/07/06 07:33:04 UTC

[jira] [Resolved] (CLOUDSTACK-8319) [VMware] VM's configuration files are left behind on source primary storage

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Likitha Shetty resolved CLOUDSTACK-8319.
----------------------------------------
    Resolution: Fixed

> [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)