You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rajesh Battala (JIRA)" <ji...@apache.org> on 2013/06/25 14:50:20 UTC
[jira] [Resolved] (CLOUDSTACK-3176) KVM DeployVM fails with unable
to get answer that is of type StartAnswer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajesh Battala resolved CLOUDSTACK-3176.
----------------------------------------
Resolution: Fixed
verified that commit f706f6757cdfcfb3fb9a288ea88e9796bc1e82d0 done by Hiroaki Kawai is fixing the issue
> KVM DeployVM fails with unable to get answer that is of type StartAnswer
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3176
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3176
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.2.0
> Reporter: Prasanna Santhanam
> Assignee: Rajesh Battala
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: 434.tar.bz2
>
>
> On the latest master, deploy VM for KVM in advanced zone fails with the following exception:
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,596 DEBUG [agent.transport.Request] (Job-Executor-99:job-96) Seq 1-1350303926: Received: { Ans: , MgmtId: 200973787296321, via: 1, Ver: v1, Flags: 10, { Answer } }
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,601 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-99:job-96) Failed to start instance VM[User|eeebdf98-5caf-4c37-a29d-65dcfab5cd1e]
> Jun 24 22:01:57 cloudstack-centos63 com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that is of class com.cloud.agent.api.StartAnswer
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:880)
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
> Jun 24 22:01:57 cloudstack-centos63 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:239)
> Jun 24 22:01:57 cloudstack-centos63 at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3308)
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2868)
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2854)
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> Jun 24 22:01:57 cloudstack-centos63 at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> Jun 24 22:01:57 cloudstack-centos63 at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> Jun 24 22:01:57 cloudstack-centos63 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> Jun 24 22:01:57 cloudstack-centos63 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> Jun 24 22:01:57 cloudstack-centos63 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> Jun 24 22:01:57 cloudstack-centos63 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> Jun 24 22:01:57 cloudstack-centos63 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> Jun 24 22:01:57 cloudstack-centos63 at java.lang.Thread.run(Thread.java:679)
--
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