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

Posted to issues@cloudstack.apache.org by "Pierre-Luc Dion (JIRA)" <ji...@apache.org> on 2016/04/13 02:59:28 UTC

[jira] [Updated] (CLOUDSTACK-8609) [VMware] VM is not accessible after a migration across clusters.

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

Pierre-Luc Dion updated CLOUDSTACK-8609:
----------------------------------------
    Fix Version/s:     (was: 4.6.1)
                   4.6.2

> [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.2
>
>
> +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)