cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre Benard <pierre.ben...@inria.fr>
Subject Unable to create a deployment for vm
Date Fri, 07 Mar 2014 10:41:35 GMT


Hi all, 




We have a problem to deploy vm and to start stopped vm on our cloudstack platform. 
But all vm already created are running (we don't have test to restart it). 




We run CS 4.2.1. Here is an ouptut of catalina.out : 




WARN [apache.cloudstack.alerts] (Job-Executor-1:job-19034 = [ 995d459a-7cc2-43a6-8a8c-a37dce4e8c22
]) alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: Failed
to deploy Vm with Id: 3545, on Host with Id: null 
INFO [user.vm.DeployVMCmd] (Job-Executor-1:job-19034 = [ 995d459a-7cc2-43a6-8a8c-a37dce4e8c22
]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment
for 
VM[User|test-pbe]Scope=interface com.cloud.dc.DataCenter; id=1 
INFO [user.vm.DeployVMCmd] (Job-Executor-1:job-19034 = [ 995d459a-7cc2-43a6-8a8c-a37dce4e8c22
]) Unable to create a deployment for VM[User|test-pbe] 
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for
VM[User|test-pbe]Scope=interface com.cloud.dc.DataCenter; id=1 
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841)

at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577) 
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)

at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)

at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3440) 
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3000) 
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2986) 
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:158) 
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) 
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:1146) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:701) 


We have ckecked all resources (CPU, RAM, IP, Primary storage, Secondary storage), all resources
are below notification treshold and disable treshold. 




We don't understand where is the origin of problem and which resource avoids new deployment.

Thanks for your help. 




Best Regards, 




Pierre BĂ©nard 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message