cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8609) [VMware] VM is not accessible after a migration across clusters.
Date Fri, 11 May 2018 11:38:00 GMT

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

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

rafaelweingartner commented on a change in pull request #2091: CLOUDSTACK-8609: [VMware] VM
is not accessible after migration across clusters
URL: https://github.com/apache/cloudstack/pull/2091#discussion_r187590015
 
 

 ##########
 File path: plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
 ##########
 @@ -2253,7 +2255,18 @@ protected StartAnswer execute(StartCommand cmd) {
 
             // Since VM was successfully powered-on, if there was an existing VM in a different
cluster that was unregistered, delete all the files associated with it.
             if (existingVmName != null && existingVmFileLayout != null) {
 
 Review comment:
   Can you extract this IF body to a method?
   This `execute` method is huge.

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

Mime
View raw message