[
https://issues.apache.org/jira/browse/CLOUDSTACK-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738499#comment-14738499
]
ASF GitHub Bot commented on CLOUDSTACK-8829:
--------------------------------------------
GitHub user maneesha-p opened a pull request:
https://github.com/apache/cloudstack/pull/797
CLOUDSTACK-8829 : Consecutive cold migration fails
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/maneesha-p/cloudstack pull-21
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/797.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #797
----
commit 8890fc638ee3ffedac873b1c6af762af3d35f273
Author: Likitha Shetty <[email protected]>
Date: 2015-09-10T09:28:04Z
CLOUDSTACK-8829 : Consecutive cold migration fails
----
> 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)
