[
https://issues.apache.org/jira/browse/CLOUDSTACK-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611771#comment-14611771
]
ASF GitHub Bot commented on CLOUDSTACK-8609:
--------------------------------------------
GitHub user likitha opened a pull request:
https://github.com/apache/cloudstack/pull/556
CLOUDSTACK-8609. [VMware] VM is not accessible after a migration acro…
…ss 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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/likitha/cloudstack CLOUDSTACK-8609
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/556.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #556
----
commit a97a402f304303af78552777d5fde56abab902e5
Author: Likitha Shetty <likitha.she...@citrix.com>
Date: 2015-05-15T08:44:37Z
CLOUDSTACK-8609. [VMware] VM is not accessible after a 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.
----
> [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: Likitha Shetty
> Fix For: 4.6.0
>
>
> +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
(v6.3.4#6332)
