[
https://issues.apache.org/jira/browse/CLOUDSTACK-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281791#comment-14281791
]
Rohit Yadav commented on CLOUDSTACK-8129:
-----------------------------------------
[~likithas] since the fix version is 4.5, can you cherry-pick the fix on 4.5?
It's not applying cleanly so I'm skipping doing it myself.
> [VMware] Cold migration of VM across VMware DCs leaves the VM behind in the
> source host.
> ----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8129
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8129
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: Future
>
>
> 1. Have an upgraded VMware setup with a legacy zone (Legacy zone is a zone
> where a CS zone has clusters that are spread across different VMware DCs). So
> ensure there are two clusters say C1 and C2 that belong to VMware DCs D1 and
> D2 respectively.
> 2. Deploy a VM. Say it is in C1.
> 3. Stop the VM.
> 3. Migrate the VM to a storage in a C2.
> 4. Start the VM.
> Observations - VM will be be successfully started in a host in C2. But a
> stale entry of the VM will be left in C1. And whenever VM sync kicks in it
> stops ans start the VM repeatedly because there are two VMs by the same name
> in vCenter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
