[
https://issues.apache.org/jira/browse/CLOUDSTACK-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588670#comment-16588670
]
ASF subversion and git services commented on CLOUDSTACK-8609:
-------------------------------------------------------------
Commit e9003fafcd9309937cd4ef79c55c9fb9489c401d in cloudstack's branch
refs/heads/master from sureshanaparti
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=e9003fa ]
CLOUDSTACK-8609: [VMware] VM is not accessible after migration across clusters
(#2091)
[VMware] VM is not accessible after migration across clusters.
Once a VM is successfully started, don't delete the files associated with the
unregistered VM, if the files are in a storage that is being used by the new VM.
Attempt to unregister a VM in another DC, only if there is a host associated
with a VM.
This closes #556
> [VMware] VM is not accessible after a migration across clusters.
> ----------------------------------------------------------------
>
> Key: CLOUDSTACK-8609
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8609
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Likitha Shetty
> Assignee: Suresh Kumar Anaparti
> Priority: Major
> Fix For: Future
>
>
> +Steps to reproduce+
> 1. Deploy a VMware zone with 2 clusters (a host each, H1 and H2) and one
> zone-wide primary storage spanning the two clusters.
> 2. Deploy a VM (VM1) on one of the hosts (H1).
> 3. Stop VM1.
> 4. Make the host that contains the VM unsuitable for further VM deployments
> - host runs out of capacity (cpu/memory)
> - host has maximum VMs deployed on it
> 5. Start VM1.
> 6. VM will be powered on H2 but will not be accessible because the .vmx and
> other VM files associated with the VM have been deleted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
