Hello,
I build a CloudStack environment using VMware 5.5 and CS 4.7. ( with local
storage enabled )
Everything working till i try to build a new VM, after i try to build a
VM, i see status staring, but i don't see any events on VMware side ( and is
not starting ) also I'm not able to delete.
SSVM and Proxy Console is up and running, reachable on private IP, also i
tested te internet connectivity from inside of SSVm and works.
The VR is also Up and running but i don't see any IP on NIC 2, i'm not
sure if this can be a issue :
Type
Traffic Type Control
Network Name
Netmask 0.0.0.0
IP Address 0.0.0.0
ID 1da1e7e7-51b4-4418-8fd9-bb5a5cf57ef1
Network ID cb974c5d-dfc2-4f7a-a57d-fd1b6b7d183e
Isolation URI
Broadcast URI
================================================================================
This is what i found for last test of VM deploy from default template, CentOS
5.3(64-bit) no GUI (vSphere):
[root@ns52XXX management]# grep -r job-33 --color
management-server.log:2016-01-25 14:32:45,588 INFO
[o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-9:ctx-0c67fce8 job-33) Add
job-33 into job monitoring
management-server.log:2016-01-25 14:32:45,603 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (catalina-exec-24:ctx-94aab038 ctx-9869fd5f)
submit async job-33, details: AsyncJobVO {id:33, userId: 2, accountId: 2,
instanceType: VirtualMachine, instanceId: 7, cmd:
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
{"serviceofferingid":"8c446bee-3419-4de0-81b0-a4405b4e95e4","keyboard":"us","cmdEventType":"VM.CREATE","ctxUserId":"2","zoneid":"9bb80e96-9d6b-4a11-b92f-9bfc754ebc89","httpmethod":"GET","templateid":"f164ac64-c393-11e5-8b5b-0cc47a7d402a","response":"json","id":"7","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"f164ac64-c393-11e5-8b5b-0cc47a7d402a\",\"com.cloud.vm.VirtualMachine\":\"533c1d9b-807a-42c6-84e1-05c38d347c43\",\"com.cloud.offering.DiskOffering\":\"8e249745-34a1-4773-8d76-2836b042514b\",\"com.cloud.dc.DataCenter\":\"9bb80e96-9d6b-4a11-b92f-9bfc754ebc89\",\"com.cloud.offering.ServiceOffering\":\"8c446bee-3419-4de0-81b0-a4405b4e95e4\"}","hypervisor":"VMware","name":"TEST11","_":"1453750363928","uuid":"533c1d9b-807a-42c6-84e1-05c38d347c43","ctxAccountId":"2","diskofferingid":"8e249745-34a1-4773-8d76-2836b042514b","ctxStartEventId":"47","displayname":"TEST11"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 37591044139110, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
management-server.log:2016-01-25 14:32:45,607 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33)
Executing AsyncJobVO {id:33, userId: 2, accountId: 2, instanceType:
VirtualMachine, instanceId: 7, cmd:
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
{"serviceofferingid":"8c446bee-3419-4de0-81b0-a4405b4e95e4","keyboard":"us","cmdEventType":"VM.CREATE","ctxUserId":"2","zoneid":"9bb80e96-9d6b-4a11-b92f-9bfc754ebc89","httpmethod":"GET","templateid":"f164ac64-c393-11e5-8b5b-0cc47a7d402a","response":"json","id":"7","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"f164ac64-c393-11e5-8b5b-0cc47a7d402a\",\"com.cloud.vm.VirtualMachine\":\"533c1d9b-807a-42c6-84e1-05c38d347c43\",\"com.cloud.offering.DiskOffering\":\"8e249745-34a1-4773-8d76-2836b042514b\",\"com.cloud.dc.DataCenter\":\"9bb80e96-9d6b-4a11-b92f-9bfc754ebc89\",\"com.cloud.offering.ServiceOffering\":\"8c446bee-3419-4de0-81b0-a4405b4e95e4\"}","hypervisor":"VMware","name":"TEST11","_":"1453750363928","uuid":"533c1d9b-807a-42c6-84e1-05c38d347c43","ctxAccountId":"2","diskofferingid":"8e249745-34a1-4773-8d76-2836b042514b","ctxStartEventId":"47","displayname":"TEST11"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 37591044139110, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
management-server.log:2016-01-25 14:32:45,664 DEBUG [c.c.n.NetworkModelImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Service SecurityGroup is
not supported in the network id=204
management-server.log:2016-01-25 14:32:45,670 DEBUG [c.c.n.NetworkModelImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Service SecurityGroup is
not supported in the network id=204
management-server.log:2016-01-25 14:32:45,687 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Deploy avoids pods: [], clusters: [], hosts: []
management-server.log:2016-01-25 14:32:45,688 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) DeploymentPlanner allocation algorithm:
com.cloud.deploy.FirstFitPlanner@5a8681fe
management-server.log:2016-01-25 14:32:45,688 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Trying to allocate a host and storage pools from dc:1,
pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
management-server.log:2016-01-25 14:32:45,688 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Is ROOT volume READY (pool already allocated)?: No
management-server.log:2016-01-25 14:32:45,688 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Searching all possible
resources under this Zone: 1
management-server.log:2016-01-25 14:32:45,689 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Listing clusters in order
of aggregate capacity, that have (atleast one host with) enough CPU and RAM
capacity under this Zone: 1
management-server.log:2016-01-25 14:32:45,693 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Removing from the
clusterId list these clusters from avoid set: []
management-server.log:2016-01-25 14:32:45,701 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Checking resources in Cluster: 1 under Pod: 1
management-server.log:2016-01-25 14:32:45,702 DEBUG
[c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68 FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1
cluster:1
management-server.log:2016-01-25 14:32:45,706 DEBUG
[c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check
for allocation: [Host[-1-Routing]]
management-server.log:2016-01-25 14:32:45,709 DEBUG
[c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68 FirstFitRoutingAllocator) Found 1 hosts for allocation after
prioritization: [Host[-1-Routing]]
management-server.log:2016-01-25 14:32:45,709 DEBUG
[c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68 FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=512
management-server.log:2016-01-25 14:32:45,717 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68 FirstFitRoutingAllocator)
Host: 1 has cpu capability (cpu:8, speed:3699) to support requested CPU: 1 and
requested speed: 500
management-server.log:2016-01-25 14:32:45,717 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68 FirstFitRoutingAllocator)
Checking if host: 1 has enough capacity for requested CPU: 500 and requested
RAM: 536870912 , cpuOverprovisioningFactor: 1.0
management-server.log:2016-01-25 14:32:45,719 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68 FirstFitRoutingAllocator)
Hosts's actual total CPU: 29592 and CPU after applying overprovisioning: 29592
management-server.log:2016-01-25 14:32:45,719 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68 FirstFitRoutingAllocator)
Free CPU: 28092 , Requested CPU: 500
management-server.log:2016-01-25 14:32:45,719 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68 FirstFitRoutingAllocator)
Free RAM: 32368287744 , Requested RAM: 536870912
management-server.log:2016-01-25 14:32:45,719 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68 FirstFitRoutingAllocator)
Host has enough CPU and RAM available
management-server.log:2016-01-25 14:32:45,719 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68 FirstFitRoutingAllocator)
STATS: Can alloc CPU from host: 1, used: 1500, reserved: 0, actual total:
29592, total with overprovisioning: 29592; requested
cpu:500,alloc_from_last_host?:false ,considerReservedCapacity?: true
management-server.log:2016-01-25 14:32:45,719 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68 FirstFitRoutingAllocator)
STATS: Can alloc MEM from host: 1, used: 1879048192, reserved: 0, total:
34247335936; requested mem: 536870912,alloc_from_last_host?:false
,considerReservedCapacity?: true
management-server.log:2016-01-25 14:32:45,719 DEBUG
[c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68 FirstFitRoutingAllocator) Found a suitable host, adding to list: 1
management-server.log:2016-01-25 14:32:45,719 DEBUG
[c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68 FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts
management-server.log:2016-01-25 14:32:45,722 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Checking suitable pools for volume (Id, Type): (7,ROOT)
management-server.log:2016-01-25 14:32:45,722 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) We need to allocate new storagepool for this volume
management-server.log:2016-01-25 14:32:45,723 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Calling StoragePoolAllocators to find suitable pools
management-server.log:2016-01-25 14:32:45,723 DEBUG
[o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) LocalStoragePoolAllocator trying to find storage pool to fit the
vm
management-server.log:2016-01-25 14:32:45,726 DEBUG
[o.a.c.s.a.AbstractStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8
job-33 ctx-480f2e68) Checking if storage pool is suitable, name: null ,poolId: 1
management-server.log:2016-01-25 14:32:45,728 INFO [c.c.s.StorageManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Storage pool null (1)
does not supply IOPS capacity, assuming enough capacity
management-server.log:2016-01-25 14:32:45,729 DEBUG [c.c.s.StorageManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Checking pool 1 for
storage, totalSize: 3992708972544, usedBytes: 7591690240, usedPct:
0.0019013883286271346, disable threshold: 0.85
management-server.log:2016-01-25 14:32:45,735 DEBUG [c.c.s.StorageManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Found storage pool
xxxx.ip-1xx-xx-2xx.net Local Storage of type VMFS with overprovisioning factor 2
management-server.log:2016-01-25 14:32:45,735 DEBUG [c.c.s.StorageManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Total over provisioned
capacity calculated is 2 * 3992708972544
management-server.log:2016-01-25 14:32:45,735 DEBUG [c.c.s.StorageManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Total capacity of the
pool xxxx.ip-1xx-xx-2xx.net Local Storage id: 1 is 7985417945088
management-server.log:2016-01-25 14:32:45,736 DEBUG [c.c.s.StorageManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Checking pool: 1 for
volume allocation [Vol[7|vm=7|ROOT]], maxSize : 7985417945088,
totalAllocatedSize : 3145728000, askingSize : 2147483648, allocated disable
threshold: 0.85
management-server.log:2016-01-25 14:32:45,737 DEBUG
[o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) LocalStoragePoolAllocator returning 1 suitable storage pools
management-server.log:2016-01-25 14:32:45,737 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Checking suitable pools for volume (Id, Type): (8,DATADISK)
management-server.log:2016-01-25 14:32:45,737 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) We need to allocate new storagepool for this volume
management-server.log:2016-01-25 14:32:45,738 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Calling StoragePoolAllocators to find suitable pools
management-server.log:2016-01-25 14:32:45,738 DEBUG
[o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) LocalStoragePoolAllocator trying to find storage pool to fit the
vm
management-server.log:2016-01-25 14:32:45,738 DEBUG
[o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8
job-33 ctx-480f2e68) ClusterScopeStoragePoolAllocator looking for storage pool
management-server.log:2016-01-25 14:32:45,738 DEBUG
[o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8
job-33 ctx-480f2e68) Looking for pools in dc: 1 pod:1 cluster:1
management-server.log:2016-01-25 14:32:45,739 DEBUG
[o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8
job-33 ctx-480f2e68) Found pools matching tags: []
management-server.log:2016-01-25 14:32:45,740 DEBUG
[o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8
job-33 ctx-480f2e68) No storage pools available for shared volume allocation,
returning
management-server.log:2016-01-25 14:32:45,740 DEBUG
[o.a.c.s.a.ZoneWideStoragePoolAllocator] (API-Job-Executor-9:ctx-0c67fce8
job-33 ctx-480f2e68) ZoneWideStoragePoolAllocator to find storage pool
management-server.log:2016-01-25 14:32:45,743 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) No suitable pools found for volume: Vol[8|vm=7|DATADISK] under
cluster: 1
management-server.log:2016-01-25 14:32:45,743 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) No suitable pools found
management-server.log:2016-01-25 14:32:45,743 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) No suitable storagePools found under this Cluster: 1
management-server.log:2016-01-25 14:32:45,745 DEBUG
[c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Could not find suitable Deployment Destination for this VM under
any clusters, returning.
management-server.log:2016-01-25 14:32:45,745 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Searching all possible
resources under this Zone: 1
management-server.log:2016-01-25 14:32:45,745 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Listing clusters in order
of aggregate capacity, that have (atleast one host with) enough CPU and RAM
capacity under this Zone: 1
management-server.log:2016-01-25 14:32:45,747 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Removing from the
clusterId list these clusters from avoid set: [1]
management-server.log:2016-01-25 14:32:45,748 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) No clusters found after
removing disabled clusters and clusters in avoid list, returning.
management-server.log:2016-01-25 14:32:45,750 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Destroying vm
VM[User|i-2-7-VM] as it failed to create on Host with Id:null
management-server.log:2016-01-25 14:32:45,794 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) 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
management-server.log:2016-01-25 14:32:45,869 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Access granted to
Acct[655b8296-c394-11e5-8b5b-0cc47a7d402a-admin] to Domain:1/ by
AffinityGroupAccessChecker
management-server.log:2016-01-25 14:32:45,971 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Access granted to
Acct[655b8296-c394-11e5-8b5b-0cc47a7d402a-admin] to Domain:1/ by
AffinityGroupAccessChecker
management-server.log:2016-01-25 14:32:45,995 WARN [o.a.c.alerts]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) alertType:: 8 //
dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to
deploy Vm with Id: 7, on Host with Id: null
management-server.log:2016-01-25 14:32:46,103 INFO
[o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) com.cloud.exception.InsufficientServerCapacityException: Unable
to create a deployment for VM[User|i-2-7-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
management-server.log:2016-01-25 14:32:46,104 INFO
[o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) Unable to create a deployment for VM[User|i-2-7-VM]
management-server.log:2016-01-25 14:32:46,105 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33)
Complete async job-33, 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-2-7-VM]"}
management-server.log:2016-01-25 14:32:46,106 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33)
Publish async job-33 complete on message bus
management-server.log:2016-01-25 14:32:46,106 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33) Wake
up jobs related to job-33
management-server.log:2016-01-25 14:32:46,106 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33)
Update db status for job-33
management-server.log:2016-01-25 14:32:46,108 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33) Wake
up jobs joined with job-33 and disjoin all subjobs created from job- 33
management-server.log:2016-01-25 14:32:46,128 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-9:ctx-0c67fce8 job-33) Done
executing org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin for
job-33
management-server.log:2016-01-25 14:32:46,128 INFO
[o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-9:ctx-0c67fce8 job-33) Remove
job-33 from job monitoring
catalina.out:INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-9:ctx-0c67fce8 job-33) Add job-33 into job monitoring
catalina.out:INFO [c.c.s.StorageManagerImpl] (API-Job-Executor-9:ctx-0c67fce8
job-33 ctx-480f2e68) Storage pool null (1) does not supply IOPS capacity,
assuming enough capacity
catalina.out:WARN [o.a.c.alerts] (API-Job-Executor-9:ctx-0c67fce8 job-33
ctx-480f2e68) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId::
null // message:: Failed to deploy Vm with Id: 7, on Host with Id: null
catalina.out:INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68)
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|i-2-7-VM]Scope=interface com.cloud.dc.DataCenter; id=1
catalina.out:INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
(API-Job-Executor-9:ctx-0c67fce8 job-33 ctx-480f2e68) Unable to create a
deployment for VM[User|i-2-7-VM]
catalina.out:INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-9:ctx-0c67fce8 job-33) Remove job-33 from job monitoring
Thanks in advance !!
Regards,
Cristian
