cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8129) [VMware] Cold migration of VM across VMware DCs leaves the VM behind in the source host.
Date Fri, 26 Dec 2014 05:55:13 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258953#comment-14258953
] 

ASF subversion and git services commented on CLOUDSTACK-8129:
-------------------------------------------------------------

Commit 15b348632df2049347f58c87830be2c02eee3b61 in cloudstack's branch refs/heads/master from
[~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=15b3486 ]

CLOUDSTACK-8129. Cold migration of VM across VMware DCs leaves the VM behind in the source
host.
If VM has been cold migrated across different VMware DCs, then unregister the VM from source
host.


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

Mime
View raw message