You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/09 13:23:26 UTC

[jira] [Commented] (CLOUDSTACK-8941) NPE when migrate vm to other zone-wide pools the second time

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

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

GitHub user ustcweizhou opened a pull request:

    https://github.com/apache/cloudstack/pull/918

    CLOUDSTACK-8941: fix NPE when migrate vm to other zone-wide pools the second time

    This is because the pod_id is set to NULL at the first time when I migrate the instance to a zone-wide pool (not cluster-wide).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ustcweizhou/cloudstack NPE-storage-migration

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/918.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 #918
    
----
commit ee7348b5d79f8c9cc187adbf647574e9c404c5a0
Author: Wei Zhou <w....@tech.leaseweb.com>
Date:   2015-10-09T11:20:41Z

    CLOUDSTACK-8941: fix NPE when migrate vm to other zone-wide pools the second time

----


> NPE when migrate vm to other zone-wide pools the second time
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8941
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8941
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Wei Zhou
>            Assignee: Wei Zhou
>
> when I migrate vm to another zone wide pool, and migrate it again back or to another pool, it will fail with the following NPE:
> 2015-10-06 12:29:11,114 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-2:job-1587 = [ 72393be7-bc02-4974-b89d-53cbaa98916c ]) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> java.lang.NullPointerException
>         at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStorageMigration(VirtualMachineManagerImpl.java:1783)
>         at com.cloud.vm.VirtualMachineManagerImpl.storageMigration(VirtualMachineManagerImpl.java:1734)
>         at com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:4342)
>         at org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:166)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
>         at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:97)
>         at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:507)
> This is because the pod_id is set to NULL at the first time when I migrate the instance to a zone-wide pool (not cluster-wide).



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