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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on CLOUDSTACK-8609:
--------------------------------------------

DaanHoogland commented on issue #2091: CLOUDSTACK-8609: [VMware] VM is not accessible after migration across clusters
URL: https://github.com/apache/cloudstack/pull/2091#issuecomment-398671630
 
 
   @sureshanaparti If you have the code that addresses the comments lying around, this is the time to update. We may be able to test before RC3 for 4.11.1

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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