You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Pierre Benard <pi...@inria.fr> on 2014/03/07 11:41:35 UTC
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
Re: Unable to create a deployment for vm
Posted by Pierre Benard <pi...@inria.fr>.
Hi Geoff,
We have already restarting the service cloudstack-manager and we have increasing some tresholds (storage and memory).
But the problem stay here.
How to see if an host is in an "avoid set" ?
To force to cloudstack to re-evaluate hosts in avoid sets, is it needed to restarting all cloudstack-agent or not ?
Regards,
Pierre
----- Mail original -----
> De: "Geoff Higginbottom" <ge...@shapeblue.com>
> À: users@cloudstack.apache.org
> Cc: "Laurent Steff" <la...@inria.fr>, "Florent Paillot" <fl...@inria.fr>
> Envoyé: Vendredi 7 Mars 2014 13:24:55
> Objet: RE: Unable to create a deployment for vm
>
> 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.higginbottom@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
>
> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>
>
> ________________________________________
> From: Pierre Benard <pi...@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.
>
Re: Unable to create a deployment for vm
Posted by Pierre Benard <pi...@inria.fr>.
Hi Francois,
The couple of line before the log snippet are in relation with the problem, see it :
INFO: Server startup in 63195 ms
WARN [server.auth.SHA256SaltedUserAuthenticator] (catalina-exec-17:) The stored password for pierre.benard@inria.fr isn't in the right format for this authenticator
For another example with a debug log level we have :
...
A lot of debug lines like debug below
...
DEBUG [factory.support.DefaultListableBeanFactory] (Job-Executor-5:job-19016 = [ 7d9f2f70-28d3-4e8c-bb0a-060d7ca1c9d3 ]) Returning cached instance of singleton bean 'vMTemplatePoolDaoImpl'
DEBUG [factory.annotation.InjectionMetadata] (Job-Executor-5:job-19016 = [ 7d9f2f70-28d3-4e8c-bb0a-060d7ca1c9d3 ]) Processing injected method of bean 'org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl': AutowiredFieldElement for com.cloud.storage.dao.StoragePoolHostDao org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl.poolHostDao
DEBUG [factory.support.DefaultListableBeanFactory] (Job-Executor-5:job-19016 = [ 7d9f2f70-28d3-4e8c-bb0a-060d7ca1c9d3 ]) Returning cached instance of singleton bean 'storagePoolHostDaoImpl'
DEBUG [factory.annotation.InjectionMetadata] (Job-Executor-5:job-19016 = [ 7d9f2f70-28d3-4e8c-bb0a-060d7ca1c9d3 ]) Processing injected method of bean 'org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl': AutowiredFieldElement for private com.cloud.storage.dao.VolumeDao org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl.volumeDao
DEBUG [factory.support.DefaultListableBeanFactory] (Job-Executor-5:job-19016 = [ 7d9f2f70-28d3-4e8c-bb0a-060d7ca1c9d3 ]) Returning cached instance of singleton bean 'volumeDaoImpl'
INFO [user.vm.StartVMCmd] (Job-Executor-5:job-19016 = [ 7d9f2f70-28d3-4e8c-bb0a-060d7ca1c9d3 ]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|sawja-linux64]Scope=interface com.cloud.dc.DataCenter; id=1
...
Same informations about unable deployement ...
...
Regards,
Pierre
----- Mail original -----
> De: "Francois Gaudreault" <fg...@cloudops.com>
> À: users@cloudstack.apache.org
> Cc: "Laurent Steff" <la...@inria.fr>, "Florent Paillot" <fl...@inria.fr>
> Envoyé: Vendredi 7 Mars 2014 13:38:42
> Objet: Re: Unable to create a deployment for vm
>
> And also, you might want to look a couple lines before the log snippet you
> sent. The "real" answer will likely be there.
>
> Francois
>
>
> On Fri, Mar 7, 2014 at 7:24 AM, Geoff Higginbottom <
> geoff.higginbottom@shapeblue.com> wrote:
>
> > 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.higginbottom@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
> >
> > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> >
> >
> > ________________________________________
> > From: Pierre Benard <pi...@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.
> >
>
Re: Unable to create a deployment for vm
Posted by Francois Gaudreault <fg...@cloudops.com>.
And also, you might want to look a couple lines before the log snippet you
sent. The "real" answer will likely be there.
Francois
On Fri, Mar 7, 2014 at 7:24 AM, Geoff Higginbottom <
geoff.higginbottom@shapeblue.com> wrote:
> 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.higginbottom@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
>
> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>
>
> ________________________________________
> From: Pierre Benard <pi...@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.
>
RE: Unable to create a deployment for vm
Posted by Geoff Higginbottom <ge...@shapeblue.com>.
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.higginbottom@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
________________________________________
From: Pierre Benard <pi...@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.