cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Weller <swel...@ena.com>
Subject Re: Unable to create a deployment for VM (Additional DATADISK - API-job)
Date Thu, 10 Sep 2015 18:32:06 GMT
Cristian,

The following logs look the most interesting:

2015-09-10 19:07:19,637 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) ClusterScopeStoragePoolAllocator looking for storage pool
2015-09-10 19:07:19,637 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Looking for pools in dc: 1  pod:1  cluster:1 having tags:[Local]
2015-09-10 19:07:19,637 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Found pools matching tags: []
2015-09-10 19:07:19,638 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) No storage pools available for shared volume allocation, returning
2015-09-10 19:07:19,638 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) ZoneWideStoragePoolAllocator to find storage pool
2015-09-10 19:07:19,638 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) No suitable pools found for volume: Vol[99|vm=72|DATADISK] under cluster:
1
2015-09-10 19:07:19,638 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) No suitable pools found
2015-09-10 19:07:19,638 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) No suitable storagePools found under this Cluster: 1

Do you have any storage tags defined that would prevent the primary storage from being allocated
to from this particular cluster or host?

- Si



________________________________________
From: Cristian Ciobanu <cristian.c@istream.today>
Sent: Thursday, September 10, 2015 1:24 PM
To: users@cloudstack.apache.org
Subject: RE: Unable to create a deployment for VM (Additional DATADISK - API-job)

Hello,

   Thanks for answer and suggestion ( is a testing environment )

   Also i did a grep for the job-754, and i found more events about this problem ( I use CS
4.5.2 with KVM on CentOS-6.6, Local Storage enabled,basic network )

[root@mgcs management]# cat  *.log | grep job-754
2015-09-10 19:07:19,581 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-91:ctx-71d92d17
job-754) Add job-754 into job monitoring
2015-09-10 19:07:19,583 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (catalina-exec-21:ctx-60c7d3d4
ctx-a0298b0c ctx-9750e753) submit async job-754, details: AsyncJobVO {id:754, userId: 6, accountId:
6, instanceType: VirtualMachine, instanceId: 72, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd,
cmdInfo: {"serviceofferingid":"59bdf4c6-9cca-4f35-a050-ac6b64c74cda","cmdEventType":"VM.CREATE","ctxUserId":"6","zoneid":"a85f1632-0718-4e67-b7c6-00d566121bf4","httpmethod":"GET","templateid":"e873ac1f-b95b-48be-863e-0d81c5307995","domainid":"6aef553f-aa33-4db2-815a-1b0f0b575645","apikey":"notherealapiyfmlp2nU0S2kib-gg1JBN6_nWy-h8rYg2o2p6LBRmidFJTkxKxYT_Eao6GquFIF62sdpRQ","id":"72","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"e873ac1f-b95b-48be-863e-0d81c5307995\",\"com.cloud.vm.VirtualMachine\":\"650d158e-b3f4-4009-ab62-c64467ab785d\",\"com.cloud.offering.DiskOffering\":\"0bc04371-2d2d-4a52-8094-7f25abb1e32b\",\"com.cloud.domain.Domain\":\"6aef553f-aa33-4db2-815a-1b0f0b575645\",\"com.cloud.dc.DataCenter\":\"a85f1632-0718-4e67-b7c6-00d566121bf4\",\"com.cloud.offering.ServiceOffering\":\"59bdf4c6-9cca-4f35-a050-ac6b64c74cda\"}","name":"cadaver","account":"client_3_1","uuid":"650d158e-b3f4-4009-ab62-c64467ab785d","ctxAccountId":"6","diskofferingid":"0bc04371-2d2d-4a52-8094-7f25abb1e32b","ctxStartEventId":"1512","signature":"qJHb2yDblfKlbAYWXXVTB9oc+HY\u003d","displayname":"cadaver"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid:
14038006851726, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2015-09-10 19:07:19,583 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754) Executing AsyncJobVO {id:754, userId: 6, accountId: 6, instanceType: VirtualMachine,
instanceId: 72, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: {"serviceofferingid":"59bdf4c6-9cca-4f35-a050-ac6b64c74cda","cmdEventType":"VM.CREATE","ctxUserId":"6","zoneid":"a85f1632-0718-4e67-b7c6-00d566121bf4","httpmethod":"GET","templateid":"e873ac1f-b95b-48be-863e-0d81c5307995","domainid":"6aef553f-aa33-4db2-815a-1b0f0b575645","apikey":"notherealapiyfmlp2nU0S2kib-gg1JBN6_nWy-h8rYg2o2p6LBRmidFJTkxKxYT_Eao6GquFIF62sdpRQ","id":"72","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"e873ac1f-b95b-48be-863e-0d81c5307995\",\"com.cloud.vm.VirtualMachine\":\"650d158e-b3f4-4009-ab62-c64467ab785d\",\"com.cloud.offering.DiskOffering\":\"0bc04371-2d2d-4a52-8094-7f25abb1e32b\",\"com.cloud.domain.Domain\":\"6aef553f-aa33-4db2-815a-1b0f0b575645\",\"com.cloud.dc.DataCenter\":\"a85f1632-0718-4e67-b7c6-00d566121bf4\",\"com.cloud.offering.ServiceOffering\":\"59bdf4c6-9cca-4f35-a050-ac6b64c74cda\"}","name":"cadaver","account":"client_3_1","uuid":"650d158e-b3f4-4009-ab62-c64467ab785d","ctxAccountId":"6","diskofferingid":"0bc04371-2d2d-4a52-8094-7f25abb1e32b","ctxStartEventId":"1512","signature":"qJHb2yDblfKlbAYWXXVTB9oc+HY\u003d","displayname":"cadaver"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid:
14038006851726, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2015-09-10 19:07:19,585 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Ignoring paremeter displayvm as the caller is not authorized to pass it in
2015-09-10 19:07:19,585 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Ignoring paremeter deploymentplanner as the caller is not authorized to pass
it in
2015-09-10 19:07:19,589 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Access to Acct[d5ef6a91-1933-42f1-9704-1b4080ad79da-client_3_1] granted
to Acct[d5ef6a91-1933-42f1-9704-1b4080ad79da-client_3_1] by DomainChecker
2015-09-10 19:07:19,591 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Access to Acct[d5ef6a91-1933-42f1-9704-1b4080ad79da-client_3_1] granted
to Acct[d5ef6a91-1933-42f1-9704-1b4080ad79da-client_3_1] by DomainChecker
2015-09-10 19:07:19,593 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Access to Tmpl[203-QCOW2-203-2-9dc340ec-e3ba-3a71-bb56-bc9b7d19e1d9
granted to Acct[d5ef6a91-1933-42f1-9704-1b4080ad79da-client_3_1] by DomainChecker
2015-09-10 19:07:19,593 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Ignoring paremeter displayvm as the caller is not authorized to pass it in
2015-09-10 19:07:19,593 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Ignoring paremeter deploymentplanner as the caller is not authorized to pass
it in
2015-09-10 19:07:19,606 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Access to VM[User|i-6-72-VM] granted to Acct[d5ef6a91-1933-42f1-9704-1b4080ad79da-client_3_1]
by DomainChecker
2015-09-10 19:07:19,611 DEBUG [c.c.n.NetworkModelImpl] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Service SecurityGroup is not supported in the network id=204
2015-09-10 19:07:19,613 DEBUG [c.c.n.NetworkModelImpl] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Service SecurityGroup is not supported in the network id=204
2015-09-10 19:07:19,618 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Deploy avoids pods: [], clusters: [], hosts: []
2015-09-10 19:07:19,618 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) DeploymentPlanner allocation algorithm: com.cloud.deploy.FirstFitPlanner@4cfc6eb1
2015-09-10 19:07:19,618 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Trying to allocate a host and storage pools from dc:1, pod:null,cluster:null,
requested cpu: 7500, requested ram: 4831838208
2015-09-10 19:07:19,618 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Is ROOT volume READY (pool already allocated)?: No
2015-09-10 19:07:19,618 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Searching all possible resources under this Zone: 1
2015-09-10 19:07:19,619 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Listing clusters in order of aggregate capacity, that have (atleast one host
with) enough CPU and RAM capacity under this Zone: 1
2015-09-10 19:07:19,620 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Removing from the clusterId list these clusters from avoid set: []
2015-09-10 19:07:19,624 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Checking resources in Cluster: 1 under Pod: 1
2015-09-10 19:07:19,624 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Looking for hosts in dc: 1  pod:1  cluster:1
2015-09-10 19:07:19,625 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for
allocation: [Host[-1-Routing]]
2015-09-10 19:07:19,626 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization:
[Host[-1-Routing]]
2015-09-10 19:07:19,626 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Looking for spFeed=7500Mhz, Ram=4608
2015-09-10 19:07:19,629 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Host: 1 has cpu capability (cpu:8, speed:3700)
to support requested CPU: 3 and requested speed: 2500
2015-09-10 19:07:19,629 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Checking if host: 1 has enough capacity for
requested CPU: 7500 and requested RAM: 4831838208 , cpuOverprovisioningFactor: 1.0
2015-09-10 19:07:19,629 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Hosts's actual total CPU: 29600 and CPU after
applying overprovisioning: 29600
2015-09-10 19:07:19,629 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Free CPU: 24100 , Requested CPU: 7500
2015-09-10 19:07:19,629 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Free RAM: 28580147200 , Requested RAM: 4831838208
2015-09-10 19:07:19,629 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Host has enough CPU and RAM available
2015-09-10 19:07:19,629 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 1, used: 1500,
reserved: 4000, actual total: 29600, total with overprovisioning: 29600; requested cpu:7500,alloc_from_last_host?:false
,considerReservedCapacity?: true
2015-09-10 19:07:19,629 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 1, used: 1879048192,
reserved: 3235905536, total: 33695100928; requested mem: 4831838208,alloc_from_last_host?:false
,considerReservedCapacity?: true
2015-09-10 19:07:19,629 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Found a suitable host, adding to list: 1
2015-09-10 19:07:19,629 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18 FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts
2015-09-10 19:07:19,630 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Checking suitable pools for volume (Id, Type): (98,ROOT)
2015-09-10 19:07:19,630 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) We need to allocate new storagepool for this volume
2015-09-10 19:07:19,631 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Calling StoragePoolAllocators to find suitable pools
2015-09-10 19:07:19,631 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) LocalStoragePoolAllocator trying to find storage pool to fit the vm
2015-09-10 19:07:19,632 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Checking if storage pool is suitable, name: null ,poolId: 1
2015-09-10 19:07:19,633 INFO  [c.c.s.StorageManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Storage pool null (1) does not supply IOPS capacity, assuming enough
capacity
2015-09-10 19:07:19,633 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Checking pool 1 for storage, totalSize: 1873625808896, usedBytes: 242614878208,
usedPct: 0.12948950481791047, disable threshold: 0.85
2015-09-10 19:07:19,636 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Found storage pool host001.xxx.com Local Storage of type Filesystem
with overprovisioning factor 2
2015-09-10 19:07:19,636 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Total over provisioned capacity calculated is 2 * 1873625808896
2015-09-10 19:07:19,636 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Total capacity of the pool host001.xxx.com Local Storage id: 1 is 3747251617792
2015-09-10 19:07:19,636 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Checking pool: 1 for volume allocation [Vol[98|vm=72|ROOT]], maxSize
: 3747251617792, totalAllocatedSize : 124870400512, askingSize : 8589934592, allocated disable
threshold: 0.85
2015-09-10 19:07:19,637 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) LocalStoragePoolAllocator returning 1 suitable storage pools
2015-09-10 19:07:19,637 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Checking suitable pools for volume (Id, Type): (99,DATADISK)
2015-09-10 19:07:19,637 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) We need to allocate new storagepool for this volume
2015-09-10 19:07:19,637 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Calling StoragePoolAllocators to find suitable pools
2015-09-10 19:07:19,637 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) LocalStoragePoolAllocator trying to find storage pool to fit the vm
2015-09-10 19:07:19,637 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) ClusterScopeStoragePoolAllocator looking for storage pool
2015-09-10 19:07:19,637 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Looking for pools in dc: 1  pod:1  cluster:1 having tags:[Local]
2015-09-10 19:07:19,637 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Found pools matching tags: []
2015-09-10 19:07:19,638 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) No storage pools available for shared volume allocation, returning
2015-09-10 19:07:19,638 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) ZoneWideStoragePoolAllocator to find storage pool
2015-09-10 19:07:19,638 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) No suitable pools found for volume: Vol[99|vm=72|DATADISK] under cluster:
1
2015-09-10 19:07:19,638 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) No suitable pools found
2015-09-10 19:07:19,638 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) No suitable storagePools found under this Cluster: 1
2015-09-10 19:07:19,639 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Could not find suitable Deployment Destination for this VM under any
clusters, returning.
2015-09-10 19:07:19,639 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Searching all possible resources under this Zone: 1
2015-09-10 19:07:19,639 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Listing clusters in order of aggregate capacity, that have (atleast one host
with) enough CPU and RAM capacity under this Zone: 1
2015-09-10 19:07:19,640 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Removing from the clusterId list these clusters from avoid set: [1]
2015-09-10 19:07:19,640 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) No clusters found after removing disabled clusters and clusters in avoid list,
returning.
2015-09-10 19:07:19,641 DEBUG [c.c.v.UserVmManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Destroying vm VM[User|i-6-72-VM] as it failed to create on Host with
Id:null
2015-09-10 19:07:19,680 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) 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
2015-09-10 19:07:19,746 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Access granted to Acct[d5ef6a91-1933-42f1-9704-1b4080ad79da-client_3_1]
to Domain:3/client_3_1_cloud/ by AffinityGroupAccessChecker
2015-09-10 19:07:19,830 DEBUG [c.c.u.AccountManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Access granted to Acct[d5ef6a91-1933-42f1-9704-1b4080ad79da-client_3_1]
to Domain:3/client_3_1_cloud/ by AffinityGroupAccessChecker
2015-09-10 19:07:19,846 WARN  [o.a.c.alerts] (API-Job-Executor-91:ctx-71d92d17 job-754 ctx-38551c18)
 alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed
to deploy Vm with Id: 72, on Host with Id: null
2015-09-10 19:07:19,929 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) com.cloud.exception.InsufficientServerCapacityException: Unable to create
a deployment for VM[User|i-6-72-VM]Scope=interface com.cloud.dc.DataCenter; id=1
2015-09-10 19:07:19,929 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Unable to create a deployment for VM[User|i-6-72-VM]
2015-09-10 19:07:19,930 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754) Complete async job-754, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable
to create a deployment for VM[User|i-6-72-VM]"}
2015-09-10 19:07:19,930 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754) Publish async job-754 complete on message bus
2015-09-10 19:07:19,930 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754) Wake up jobs related to job-754
2015-09-10 19:07:19,930 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754) Update db status for job-754
2015-09-10 19:07:19,931 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754) Wake up jobs joined with job-754 and disjoin all subjobs created from job- 754
2015-09-10 19:07:19,946 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-91:ctx-71d92d17
job-754) Done executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-754
2015-09-10 19:07:19,946 INFO  [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-91:ctx-71d92d17
job-754) Remove job-754 from job monitoring




Thanks!

Regards,
Cristian


On 9/10/2015 9:03:48 PM, Somesh Naidu <somesh.naidu@citrix.com> wrote:
Cristian,

First off, I would recommend masking information such as apikey, signature, public IPs, etc.
when posting on the list for security reasons.

The reason for failure as per logs is "InsufficientServerCapacityException" however, from
the logs snippets it is not possible to find the root cause. Also, I suspect the "InsufficientServerCapacityException"
is a consequential error, that is, result of all the compute/storage resources ending up in
the avoid set. What caused the compute/storage resource to end up in that list is the root
cause. You should trace "job-754" and look for the initial failure.

Alternately, you could compare API call you're using vs the one generated via CS GUI to see
for any differences. It will also help to know version of CS (looks like pre 4.5) and hypervisor.

Regards,
Somesh

-----Original Message-----
From: Cristian Ciobanu [mailto:cristian.c@istream.today]
Sent: Thursday, September 10, 2015 1:18 PM
To: users@cloudstack.apache.org
Subject: Unable to create a deployment for VM (Additional DATADISK - API-job)


Hello,

    I have a problem when i try to deploy a VM with DATADISK via API, i don't have any issue
when i deploy from the CS interface.

I found some logs on CS MGMT:

==> management-server.log <==>
2015-09-10 19:07:19,584 DEBUG [c.c.a.ApiServlet] (catalina-exec-21:ctx-60c7d3d4 ctx-a0298b0c
ctx-9750e753) ===END===  5.172.233.323 -- GET  account=client_3_1&apikey=nZsd2olHQnj4ApdsWyfmlp2nU0S2kib-gg1JBN6_nWy-h8rYg2o2p6LBRmidFJTkxKxYT_Eao6GquFIF62sdpRQ&command=deployVirtualMachine&diskofferingid=0bc04371-2d2d-4a52-8094-7f25abb1e32b&displayname=cadaver&domainid=6aef553f-aa33-4db2-815a-1b0f0b575645&name=cadaver&response=json&serviceofferingid=59bdsd4c6-9cca-4f35-a050-ac6b64c74cda&templateid=e873ac1f-b95b-48be-863e-0d81c5307995&zoneid=a85f1632-0718-4e67-b7c6-00d566121bf4&signature=qJHb2yDblfKlbAYWXXVTB9oc%2BHY%3D
2015-09-10 19:07:19,585 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Ignoring paremeter displayvm as the caller is not authorized to pass it in
2015-09-10 19:07:19,585 DEBUG [o.a.c.a.BaseCmd] (API-Job-Executor-91:ctx-71d92d17 job-754
ctx-38551c18) Ignoring paremeter deploymentplanner as the caller is not authorized to pass
it in
=======================================================================

2015-09-10 19:07:19,846 WARN  [o.a.c.alerts] (API-Job-Executor-91:ctx-71d92d17 job-754 ctx-38551c18)
 alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed
to deploy Vm with Id: 72, on Host with Id: null
2015-09-10 19:07:19,929 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) com.cloud.exception.InsufficientServerCapacityException: Unable to create
a deployment for VM[User|i-6-72-VM]Scope=interface com.cloud.dc.DataCenter; id=1
2015-09-10 19:07:19,929 INFO  [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-91:ctx-71d92d17
job-754 ctx-38551c18) Unable to create a deployment for VM[User|i-6-72-VM]
======================================================================

Can i get some help ? Thanks !


Regards,
Cristian



Mime
View raw message