You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/06/20 01:22:21 UTC

[jira] [Assigned] (CLOUDSTACK-1678) Destroying errored out VM deployment fails with NPE

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

Alena Prokharchyk reassigned CLOUDSTACK-1678:
---------------------------------------------

    Assignee: Alena Prokharchyk
    
> Destroying errored out VM deployment fails with NPE
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-1678
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1678
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Management Server
>    Affects Versions: 4.0.1
>         Environment: EL6.3 - KVM 4.0.1
>            Reporter: David Nalley
>            Assignee: Alena Prokharchyk
>
> Steps to reproduce: 
> * Attempt to deploy an instance that will fail (in this case deploying with a service offering with a storage tag that doesn't exist) 
> * Watch deployment error out (VM shows up as error in list of instances) 
> * Attempt to destroy the instance. 
> * See the following exception. 
> 2013-03-14 02:27:32,374 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) ===START===  70.194.132.238 -- GET  command=destroyVirtualMachine&id=d65e6997-f26a-499f-ba38-f2b8908d0200&response=json&sessionkey=YZBscdunOv2wR%2FOHDtAS8LpkylM%3D&_=1363242452991
> 2013-03-14 02:27:32,531 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-1:null) submit async job-238, details: AsyncJobVO {id:238, userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine, instanceId: 89, cmd: com.cloud.api.commands.DestroyVMCmd, cmdOriginator: null, cmdInfo: {"response":"json","id":"d65e6997-f26a-499f-ba38-f2b8908d0200","sessionkey":"YZBscdunOv2wR/OHDtAS8LpkylM\u003d","ctxUserId":"2","_":"1363242452991","ctxAccountId":"2","ctxStartEventId":"1062"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 206915886132947, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-14 02:27:32,534 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-142:job-238) Executing com.cloud.api.commands.DestroyVMCmd for job-238
> 2013-03-14 02:27:32,535 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) ===END===  70.194.132.238 -- GET  command=destroyVirtualMachine&id=d65e6997-f26a-499f-ba38-f2b8908d0200&response=json&sessionkey=YZBscdunOv2wR%2FOHDtAS8LpkylM%3D&_=1363242452991
> 2013-03-14 02:27:32,593 ERROR [cloud.api.ApiDispatcher] (Job-Executor-142:job-238) Exception while executing DestroyVMCmd:
> java.lang.NullPointerException
>         at com.cloud.utils.AnnotationHelper.getTableName(AnnotationHelper.java:34)
>         at com.cloud.utils.exception.RuntimeCloudException.addProxyObject(RuntimeCloudException.java:53)
>         at com.cloud.vm.UserVmManagerImpl.getHypervisorTypeOfUserVM(UserVmManagerImpl.java:3260)
>         at com.cloud.api.commands.DestroyVMCmd.execute(DestroyVMCmd.java:101)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
>         at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:722)
> 2013-03-14 02:27:32,597 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-142:job-238) Complete async job-238, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira