Good to hear that Diego!! If you think you followed the steps correctly then you can file a bug for this issue here: https://issues.apache.org/jira/browse/CLOUDSTACK
--Sanjay From: Diego Spinola Castro [mailto:spinolacas...@gmail.com] Sent: Monday, November 25, 2013 5:28 PM To: Sanjay Tripathi Subject: Re: Unable add instance after update on CS4.2 Hi Sanjay. I figured out what was wrong. the total_capacity field of op_host_capacity table wasn't updated when i change the overprovisioning factor. i just updated the value and everthing works fine. 2013/11/25 Sanjay Tripathi <sanjay.tripa...@citrix.com<mailto:sanjay.tripa...@citrix.com>> Hi Diego, >From the listClusters response, it looks like your cluster doesn't have enough >CPU capacity to deploy a new VM. Type = 1 is for CPU resource. { "capacitytotal": 576000, "capacityused": 701250, "percentused": "121.74", "type": 1 } --Sanjay > -----Original Message----- > From: Diego Spinola Castro > [mailto:spinolacas...@gmail.com<mailto:spinolacas...@gmail.com>] > Sent: Monday, November 25, 2013 1:11 AM > To: us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org> > Subject: Unable add instance after update on CS4.2 > > Hi guys, i'm running into a issue on a vmware 4.1 cluster after update CS to > 4.2. > > When i try create a instance i get the following error: > > 2013-11-24 17:37:43,817 DEBUG [cloud.api.ApiServlet] > (catalina-exec-11:null) ===START=== 187.37.35.156 -- GET > command=deployVirtualMachine&zoneId=83a1d5a6-6534-4600-b8b4- > c1bd240eb711&templateId=227&hypervisor=VMware&serviceOfferingId=32 > &networkIds=0749b01c-9dbe-4008-a388- > c6cb82988852&response=json&sessionkey=%2BrE4mGxi%2Bnqu2r7FxFj8QE > V9%2FFA%3D&_=1385321825263 > 2013-11-24 17:37:43,858 DEBUG [cloud.api.ApiDispatcher] > (catalina-exec-11:null) InfrastructureEntity name > is:com.cloud.offering.ServiceOffering > 2013-11-24 17:37:43,858 DEBUG [cloud.api.ApiDispatcher] > (catalina-exec-11:null) ControlledEntity name > is:com.cloud.template.VirtualMachineTemplate > 2013-11-24 17:37:43,863 DEBUG [cloud.api.ApiDispatcher] > (catalina-exec-11:null) ControlledEntity name is:com.cloud.network.Network > 2013-11-24 17:37:43,869 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-11:null) Access to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:43,873 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-11:null) Access to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:43,878 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-11:null) Access to Ntwk[358|Guest|6] granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:43,881 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-11:null) Access to > Tmpl[227-OVA-227-2-150da313-1018-3320-becd-9dc003c96374 granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:43,884 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-11:null) Access to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:43,913 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-11:null) Access to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:43,964 DEBUG [cloud.network.NetworkModelImpl] > (catalina-exec-11:null) Service SecurityGroup is not supported in the network > id=358 > 2013-11-24 17:37:44,144 DEBUG [cloud.vm.UserVmManagerImpl] > (catalina-exec-11:null) Allocating in the DB for vm > 2013-11-24 17:37:44,224 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (catalina-exec-11:null) Allocating entries for VM: > VM[User|ab62df84-e398-4e02-8a55-9319ed694998] > 2013-11-24 17:37:44,238 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (catalina-exec-11:null) Allocating nics for VM[User|ab62df84-e398-4e02- > 8a55-9319ed694998] > 2013-11-24 17:37:44,240 DEBUG [cloud.network.NetworkManagerImpl] > (catalina-exec-11:null) Allocating nic for vm VM[User|ab62df84-e398-4e02- > 8a55-9319ed694998] in network Ntwk[358|Guest|6] with requested profile > NicProfile[0-0-null-null-null > 2013-11-24 17:37:44,358 DEBUG [cloud.network.NetworkModelImpl] > (catalina-exec-11:null) Service SecurityGroup is not supported in the network > id=358 > 2013-11-24 17:37:44,361 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (catalina-exec-11:null) Allocating disks for VM[User|ab62df84-e398-4e02- > 8a55-9319ed694998] > 2013-11-24 17:37:44,389 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (catalina-exec-11:null) Allocation completed for VM: > VM[User|ab62df84-e398-4e02-8a55-9319ed694998] > 2013-11-24 17:37:44,389 DEBUG [cloud.vm.UserVmManagerImpl] > (catalina-exec-11:null) Successfully allocated DB entry for > VM[User|ab62df84-e398-4e02-8a55-9319ed694998] > 2013-11-24 17:37:44,566 DEBUG [cloud.network.NetworkModelImpl] > (catalina-exec-11:null) Service SecurityGroup is not supported in the network > id=358 > 2013-11-24 17:37:44,573 DEBUG [cloud.network.NetworkModelImpl] > (catalina-exec-11:null) Service SecurityGroup is not supported in the network > id=358 > 2013-11-24 17:37:44,968 DEBUG [cloud.async.AsyncJobManagerImpl] > (catalina-exec-11:null) submit async job-470 = [ 066b7455-3b86-4b85-9954- > 7caf6ddb710e ], details: AsyncJobVO {id:470, > userId: 343, accountId: 165, sessionKey: null, instanceType: > VirtualMachine, instanceId: 1074, cmd: > org.apache.cloudstack.api.command.user.vm.DeployVMCmd, > cmdOriginator: null, > cmdInfo: > {"sessionkey":"+rE4mGxi+nqu2r7FxFj8QEV9/FA\u003d","cmdEventType":"V > M.CREATE","ctxUserId":"343","serviceOfferingId":"32","httpmethod":"GET", > "zoneId":"83a1d5a6-6534-4600-b8b4- > c1bd240eb711","templateId":"227","response":"json","id":"1074","networkI > ds":"0749b01c-9dbe-4008-a388- > c6cb82988852","hypervisor":"VMware","_":"1385321825263","ctxAccountId": > "165","ctxStartEventId":"193267"}, > cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, > processStatus: 0, resultCode: 0, result: null, initMsid: 132226478205, > completeMsid: null, lastUpdated: null, lastPolled: null, created: null} > 2013-11-24 17:37:44,973 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd for > job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ] > 2013-11-24 17:37:44,974 DEBUG [cloud.api.ApiServlet] > (catalina-exec-11:null) ===END=== 187.37.35.156 -- GET > command=deployVirtualMachine&zoneId=83a1d5a6-6534-4600-b8b4- > c1bd240eb711&templateId=227&hypervisor=VMware&serviceOfferingId=32 > &networkIds=0749b01c-9dbe-4008-a388- > c6cb82988852&response=json&sessionkey=%2BrE4mGxi%2Bnqu2r7FxFj8QE > V9%2FFA%3D&_=1385321825263 > 2013-11-24 17:37:44,974 DEBUG [cloud.api.ApiServlet] > (catalina-exec-11:null) ===END=== 187.37.35.156 -- GET > command=deployVirtualMachine&zoneId=83a1d5a6-6534-4600-b8b4- > c1bd240eb711&templateId=227&hypervisor=VMware&serviceOfferingId=32 > &networkIds=0749b01c-9dbe-4008-a388- > c6cb82988852&response=json&sessionkey=%2BrE4mGxi%2Bnqu2r7FxFj8QE > V9%2FFA%3D&_=1385321825263 > 2013-11-24 17:37:44,988 DEBUG [cloud.api.ApiDispatcher] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > InfrastructureEntity name is:com.cloud.offering.ServiceOffering > 2013-11-24 17:37:44,989 DEBUG [cloud.api.ApiDispatcher] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > ControlledEntity name is:com.cloud.template.VirtualMachineTemplate > 2013-11-24 17:37:44,994 DEBUG [cloud.api.ApiDispatcher] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > ControlledEntity name is:com.cloud.network.Network > 2013-11-24 17:37:44,999 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Access to Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:45,002 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Access to Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:45,007 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Access to Ntwk[358|Guest|6] granted to Acct[8bcd7766-9361-40a9-b660- > eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:45,010 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Access to Tmpl[227-OVA-227-2-150da313-1018-3320-becd-9dc003c96374 > granted to Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:45,154 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Access to VM[User|ab62df84-e398-4e02-8a55-9319ed694998] granted to > Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by > DomainChecker_EnhancerByCloudStack_560d9237 > 2013-11-24 17:37:45,173 DEBUG [cloud.network.NetworkModelImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Service SecurityGroup is not supported in the network id=358 > 2013-11-24 17:37:45,179 DEBUG [cloud.network.NetworkModelImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Service SecurityGroup is not supported in the network id=358 > 2013-11-24 17:37:45,212 DEBUG > [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Deploy avoids pods: [], clusters: [], hosts: [] > 2013-11-24 17:37:45,251 DEBUG > [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > DeploymentPlanner allocation algorithm: > com.cloud.deploy.UserConcentratedPodPlanner_EnhancerByCloudStack_42 > 441383@353a2aeb > 2013-11-24 17:37:45,251 DEBUG > [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) Trying > to allocate a host and storage pools from dc:1, pod:null,cluster:null, > requested cpu: 500, requested ram: 536870912 > 2013-11-24 17:37:45,251 DEBUG > [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) Is > ROOT volume READY (pool already allocated)?: No > 2013-11-24 17:37:45,251 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Searching all possible resources under this Zone: 1 > 2013-11-24 17:37:45,253 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Listing clusters in order of aggregate capacity, that have (atleast one host > with) enough CPU and RAM capacity under this Zone: 1 > 2013-11-24 17:37:45,259 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Removing from the clusterId list these clusters from avoid set: [] > 2013-11-24 17:37:45,267 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Cannot allocate cluster list [1] for vm creation since their allocated > percentage crosses the disable capacity threshold defined at each cluster/ at > global value for capacity Type : 1, skipping these clusters > 2013-11-24 17:37:45,291 DEBUG > [cloud.deploy.UserConcentratedPodPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Applying UserConcentratedPod heuristic for account: 165 > 2013-11-24 17:37:45,294 DEBUG > [cloud.deploy.UserConcentratedPodPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Reordering cluster list as per pods ordered by user concentration > 2013-11-24 17:37:45,297 DEBUG > [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Cluster: 2 has HyperVisorType that does not match the VM, skipping this > cluster > 2013-11-24 17:37:45,297 DEBUG > [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) Could > not find suitable Deployment Destination for this VM under any clusters, > returning. > 2013-11-24 17:37:45,298 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Searching all possible resources under this Zone: 1 > 2013-11-24 17:37:45,299 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Listing clusters in order of aggregate capacity, that have (atleast one host > with) enough CPU and RAM capacity under this Zone: 1 > 2013-11-24 17:37:45,303 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Removing from the clusterId list these clusters from avoid set: [2] > 2013-11-24 17:37:45,310 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Cannot allocate cluster list [1] for vm creation since their allocated > percentage crosses the disable capacity threshold defined at each cluster/ at > global value for capacity Type : 1, skipping these clusters > 2013-11-24 17:37:45,310 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) No > clusters found after removing disabled clusters and clusters in avoid list, > returning. > 2013-11-24 17:37:45,315 DEBUG [cloud.vm.UserVmManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Destroying vm VM[User|ab62df84-e398-4e02-8a55-9319ed694998] as it > failed to create on Host with Id:null > 2013-11-24 17:37:45,583 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) 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-11-24 17:37:45,898 WARN [apache.cloudstack.alerts] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // > message:: Failed to deploy Vm with Id: 1074, on Host with Id: null > 2013-11-24 17:37:46,534 INFO [user.vm.DeployVMCmd] (Job-Executor-1:job- > 470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > com.cloud.exception.InsufficientServerCapacityException: Unable to create > a deployment for VM[User|ab62df84-e398-4e02-8a55- > 9319ed694998]Scope=interface > com.cloud.dc.DataCenter; id=1 > 2013-11-24 17:37:46,534 INFO [user.vm.DeployVMCmd] (Job-Executor-1:job- > 470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) Unable to create a > deployment for VM[User|ab62df84-e398-4e02-8a55-9319ed694998] > com.cloud.exception.InsufficientServerCapacityException: Unable to create > a deployment for VM[User|ab62df84-e398-4e02-8a55- > 9319ed694998]Scope=interface > com.cloud.dc.DataCenter; id=1 > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserv > eVirtualMachine(VMEntityManagerImpl.java:209) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.res > erve(VirtualMachineEntityImpl.java:198) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerI > mpl.java:3405) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerI > mpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerI > mpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$Intercep > torDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(Deplo > yVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:5 > 31) > 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.jav > a:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja > va:615) > at java.lang.Thread.run(Thread.java:701) > 2013-11-24 17:37:46,538 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-1:job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ]) > Complete async job-470 = [ 066b7455-3b86-4b85-9954-7caf6ddb710e ], > jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable to > create a deployment for VM[User|ab62df84-e398-4e02-8a55-9319ed694998] > > > > > Does'n matter how i increase cpu.overprovisioning.factor . It's in 5 and i > still > can't allocate vm. > > Following the result of listCluster api call: > > [root@cloud ~]# curl -sS " > http://localhost:8096/?command=listClusters&showcapacities=true&id=1&r > esponse=json" > | python -mjson.tool > { > "listclustersresponse": { > "cluster": [ > { > "allocationstate": "Enabled", > "capacity": [ > { > "capacitytotal": 13020461793280, > "capacityused": 8827240284160, > "percentused": "67.8", > "type": 3 > }, > { > "capacitytotal": 558206521344, > "capacityused": 282662535168, > "percentused": "50.64", > "type": 0 > }, > { > "capacitytotal": 13020461793280, > "capacityused": 4702019256320, > "percentused": "36.11", > "type": 2 > }, > { > "capacitytotal": 576000, > "capacityused": 701250, > "percentused": "121.74", > "type": 1 > } > ], > "clustertype": "ExternalManaged", > "cpuovercommitratio": "5", > "hypervisortype": "VMware", > "id": "1", > "managedstate": "Managed", > "memoryovercommitratio": "1", > "name": > "10.16.140.20/TELIUMSPO/Telium_Cloud<http://10.16.140.20/TELIUMSPO/Telium_Cloud>", > "podid": "1", > "podname": "TELIUM-SPO01", > "zoneid": "83a1d5a6-6534-4600-b8b4-c1bd240eb711", > "zonename": "TELIUMSPO" > } > ], > "count": 1 > } > } > > > > What is wrong? Doing the math , i would be able to use up to (576000 * 5 ) > mhz, wouldn't it ?