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/07/01 13:02:19 UTC
[jira] [Commented] (CLOUDSTACK-3301) NPE wile deployVM in kvm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696723#comment-13696723 ]
Rajesh Battala commented on CLOUDSTACK-3301:
--------------------------------------------
This issue is reproduced with KVM, ZWPS and NFS as datastore.
this issue won't occur in cluster wide storage.
> NPE wile deployVM in kvm
> ------------------------
>
> Key: CLOUDSTACK-3301
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3301
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: KVM, Storage Controller
> Affects Versions: 4.2.0
> Reporter: Rajesh Battala
> Assignee: Rajesh Battala
> Priority: Blocker
> Fix For: 4.2.0
>
>
> while creation VM on KVM with ZWPS
> deploy VM is failing with the below NPE exception log.
> reason:
> ======
> from the code pool capacity iops is getting set only for solidfire storage type not for nfs.
> Need to handle the case for it.
> 2013-07-01 15:45:42,224 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-7:job-19) VM state transitted from :Stopped to Error with event: OperationFailedToErrorvm's original host id: null new host id: null host id before state transition: null
> 2013-07-01 15:45:42,232 WARN [apache.cloudstack.alerts] (Job-Executor-7:job-19) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 10, on Host with Id: null
> 2013-07-01 15:45:42,276 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-7:job-19) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd
> java.lang.NullPointerException
> at com.cloud.storage.StorageManagerImpl.storagePoolHasEnoughIops(StorageManagerImpl.java:1518)
> at org.apache.cloudstack.storage.allocator.ZoneWideStoragePoolAllocator.filter(ZoneWideStoragePoolAllocator.java:53)
> at org.apache.cloudstack.storage.allocator.ZoneWideStoragePoolAllocator.select(ZoneWideStoragePoolAllocator.java:96)
> at org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.allocateToPool(AbstractStoragePoolAllocator.java:109)
> at com.cloud.deploy.DeploymentPlanningManagerImpl.findSuitablePoolsForVolumes(DeploymentPlanningManagerImpl.java:1123)
> at com.cloud.deploy.DeploymentPlanningManagerImpl.checkClustersforDestination(DeploymentPlanningManagerImpl.java:847)
> at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:404)
> at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186)
> at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3307)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2868)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2854)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> 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)
--
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