Pierre,

Sometimes a host gets put into an 'avoid set' which means its not available for 
new deployments.

One way of forcing CloudStack to re-evaluate hosts in avoid sets is to restart 
the cloudstack management service

You say that resources all below thresholds, but would they be if this VM is 
actually started?  As a test, before you restart the management service, try 
increasing the disable thresholds (which require a restart to take effect) then 
see if you can start the VM.

Kind Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS


________________________________________
From: Pierre Benard <pierre.ben...@inria.fr>
Sent: 07 March 2014 10:41
To: users@cloudstack.apache.org
Cc: Laurent Steff; Florent Paillot
Subject: Unable to create a deployment for vm

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
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
18th-19th February 2014, Brazil. 
Classroom<http://shapeblue.com/cloudstack-training/>
17th-23rd March 2014, Region A. Instructor led, 
On-line<http://shapeblue.com/cloudstack-training/>
24th-28th March 2014, Region B. Instructor led, 
On-line<http://shapeblue.com/cloudstack-training/>
16th-20th June 2014, Region A. Instructor led, 
On-line<http://shapeblue.com/cloudstack-training/>
23rd-27th June 2014, Region B. Instructor led, 
On-line<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Reply via email to