cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Kumar Anaparti (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-8609) [VMware] VM is not accessible after a migration across clusters.
Date Tue, 09 May 2017 19:27:04 GMT

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

Suresh Kumar Anaparti reassigned CLOUDSTACK-8609:
-------------------------------------------------

    Assignee: Suresh Kumar Anaparti  (was: Likitha Shetty)

> [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
>             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
(v6.3.15#6346)

Mime
View raw message