Hi Gokhan,

You need to trace the logs prior to this to see why the hosts were put in avoid 
set. 
There should be some error that caused the deployment to fail on these hosts, 
causing CloudStack to flag them as 'should be avoided'.

Thanks,
Prachi


-----Original Message-----
From: Jayapal Reddy Uradi [mailto:jayapalreddy.ur...@citrix.com] 
Sent: Tuesday, April 22, 2014 2:00 AM
To: <users@cloudstack.apache.org>
Subject: Re: Insufficient capacity exception

Hi,

>From the below logs the hosts are in avoid set.
VM created failed because of no suitable host found.

Can you please check the MS logs for errors/exception while starting vm 
deployment ?
 

(Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) Host
name: host2, hostId: 4 is in avoid set, skipping this and trying other 
available hosts
2014-04-22 10:58:50,616 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
(Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) Host
name: host1, hostId: 1 is in avoid set, skipping this and trying other 
available hosts
2014-04-22 10:58:50,616 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
(Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) Host 
Allocator returning 0 suitable hosts


Thanks,
Jayapal
On 22-Apr-2014, at 1:32 PM, gokhan kocaman <gokhank...@gmail.com> wrote:

> Hi,
> 
> I have enough resources on my hosts (ram,cpu ...)
> 
> But I got error while try to create vm.
> 
> Log is:
> 
> 2014-04-22 10:58:50,555 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Successfully transitioned 
> to start state for VM[User|yuyu] reservation id = 
> c93b30c1-3cfa-4bbe-86cc-bd21eee7d62e
> 2014-04-22 10:58:50,603 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Trying to deploy VM, vm 
> has
> dcId: 1 and podId: 1
> 2014-04-22 10:58:50,603 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Deploy avoids pods: [],
> clusters: [], hosts: [1, 4]
> 2014-04-22 10:58:50,607 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Deploy avoids pods: [],
> clusters: [], hosts: [1, 4]
> 2014-04-22 10:58:50,608 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) DeploymentPlanner 
> allocation
> algorithm: com.cloud.deploy.FirstFitPlanner@21a24ed3
> 2014-04-22 10:58:50,608 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Trying to allocate a host 
> and storage pools from dc:1, pod:1,cluster:null, requested cpu: 500, 
> requested
> ram: 536870912
> 2014-04-22 10:58:50,608 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Is ROOT volume READY (pool 
> already allocated)?: No
> 2014-04-22 10:58:50,608 DEBUG [c.c.d.FirstFitPlanner]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Searching resources only 
> under specified Pod: 1
> 2014-04-22 10:58:50,608 DEBUG [c.c.d.FirstFitPlanner]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Listing clusters in order 
> of aggregate capacity, that have (atleast one host with) enough CPU 
> and RAM capacity under this Pod: 1
> 2014-04-22 10:58:50,610 DEBUG [c.c.d.FirstFitPlanner]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Removing from the 
> clusterId list these clusters from avoid set: []
> 2014-04-22 10:58:50,613 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Checking resources in Cluster:
> 1 under Pod: 1
> 2014-04-22 10:58:50,613 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) 
> Looking for hosts in dc: 1  pod:1  cluster:1
> 2014-04-22 10:58:50,614 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) 
> FirstFitAllocator has 2 hosts to check for allocation: 
> [Host[-4-Routing], Host[-1-Routing]]
> 2014-04-22 10:58:50,616 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) 
> Found
> 2 hosts for allocation after prioritization: [Host[-4-Routing], 
> Host[-1-Routing]]
> 2014-04-22 10:58:50,616 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) 
> Looking for speed=500Mhz, Ram=512
> 2014-04-22 10:58:50,616 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) 
> Host
> name: host2, hostId: 4 is in avoid set, skipping this and trying other 
> available hosts
> 2014-04-22 10:58:50,616 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) 
> Host
> name: host1, hostId: 1 is in avoid set, skipping this and trying other 
> available hosts
> 2014-04-22 10:58:50,616 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69 FirstFitRoutingAllocator) 
> Host Allocator returning 0 suitable hosts
> 2014-04-22 10:58:50,616 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) No suitable hosts found
> 2014-04-22 10:58:50,616 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) No suitable hosts found 
> under this Cluster: 1
> 2014-04-22 10:58:50,617 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Could not find suitable 
> Deployment Destination for this VM under any clusters, returning.
> 2014-04-22 10:58:50,617 DEBUG [c.c.d.FirstFitPlanner]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Searching resources only 
> under specified Pod: 1
> 2014-04-22 10:58:50,617 DEBUG [c.c.d.FirstFitPlanner]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Listing clusters in order 
> of aggregate capacity, that have (atleast one host with) enough CPU 
> and RAM capacity under this Pod: 1
> 2014-04-22 10:58:50,618 DEBUG [c.c.d.FirstFitPlanner]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Removing from the 
> clusterId list these clusters from avoid set: [1]
> 2014-04-22 10:58:50,618 DEBUG [c.c.d.FirstFitPlanner]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) No clusters found after 
> removing disabled clusters and clusters in avoid list, returning.
> 2014-04-22 10:58:50,711 DEBUG [c.c.c.CapacityManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) VM state transitted from 
> :Starting to Stopped with event: OperationFailedvm's original host id: 
> null new host id: null host id before state transition: null
> 2014-04-22 10:58:50,763 DEBUG [c.c.v.UserVmManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) Destroying vm 
> VM[User|yuyu] as it failed to create on Host with Id:null
> 2014-04-22 10:58:50,863 DEBUG [c.c.c.CapacityManagerImpl]
> (Job-Executor-51:ctx-4325fdf4 ctx-86395c69) 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
> 2014-04-22 10:58:50,984 WARN  [o.a.c.alerts] 
> (Job-Executor-51:ctx-4325fdf4
> ctx-86395c69)  alertType:: 8 // dataCenterId:: 1 // podId:: 1 //
> clusterId:: null // message:: Failed to deploy Vm with Id: 46, on Host 
> with
> Id: null
> 2014-04-22 10:58:51,535 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-51:ctx-4325fdf4) Unexpected exception while executing 
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM 
> due to insufficient capacity
>    at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605)
>    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:207)
>    at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581)
>    at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161)
>    at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147)
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>    at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>    at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>    at java.lang.reflect.Method.invoke(Method.java:606)
>    at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
>    at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
>    at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
>    at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
>    at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
>    at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
>    at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
>    at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
>    at com.sun.proxy.$Proxy169.startVirtualMachine(Unknown Source)
>    at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443)
>    at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
>    at
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
>    at
> com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
>    at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>    at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>    at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>    at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
>    at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509)
>    at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>    at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>    at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>    at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>    at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>    at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>    at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>    at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>    at java.lang.Thread.run(Thread.java:744)
> Caused by: com.cloud.exception.InsufficientServerCapacityException: 
> Unable to create a deployment for VM[User|yuyu]Scope=interface 
> com.cloud.dc.DataCenter; id=1
>    at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:921)
>    at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
>    at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:601)
>    ... 37 more

Reply via email to