cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maneesha (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CLOUDSTACK-8829) Consecutive cold migration fails
Date Mon, 14 Sep 2015 11:45:45 GMT

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

Maneesha edited comment on CLOUDSTACK-8829 at 9/14/15 11:45 AM:
----------------------------------------------------------------

Author - Likitha Shetty <likitha.shetty@citrix.com>
Issue
Consecutive VM cold migration fails.
Root Cause Analysis
In case of VMware, if VM is being cold migrated between clusters belonging to two different
VMware DCs, Cloudstack unregisters the VM from the source host and cleans up the associated
VM files. The check if a VM is being cold migrated across DCs is made using the source host
id. In case of consecutive cold migrations since the source host id of a VM is NULL and no
VM exists, Cloudstack should skip the check
Proposed Solution
Attempt to unregister a VM in another DC, only if there is a host associated with a VM.


was (Author: maneeshap):
Author - Likitha Shetty <likitha.shetty@citrix.com>
Issue
Consecutive VM cold migration fails.
Root Cause Analysis
In case of VMware, if VM is being cold migrated between clusters belonging to two different
VMware DCs, CCP unregisters the VM from the source host and cleans up the associated VM files.
The check if a VM is being cold migrated across DCs is made using the source host id. In case
of consecutive cold migrations since the source host id of a VM is NULL and no VM exists,
CCP should skip the check
Proposed Solution
Attempt to unregister a VM in another DC, only if there is a host associated with a VM.

> Consecutive cold migration fails
> --------------------------------
>
>                 Key: CLOUDSTACK-8829
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8829
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Maneesha
>
> The following scenario is broken:
> 1.	Deploy VM and stop it
> 2.	Migrate stopped VM to a different primary storage pool
> 3.	Again migrate the same VM to another/same storage pool. Fails with NPE.
> java.lang.NullPointerException
>         at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStorageMigration(VirtualMachineManagerImpl.java:1745)
>         at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStorageMigration(VirtualMachineManagerImpl.java:4716)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:606)
>         at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
>         at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4723)
>         at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:103)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message