Well, this one still doesn't provide any usefull info. 1. Can you confirm if you have tags set on LXC Compute Offerings or any storage used by LXC cluster? 2. Consider change logging level for management-server.log to TRACE mode, which will show also all SQL queries executed, so perhaps we can see why it craps out. 3. Not meant to discourage you, but I'm not sure weather LXC code still works with any more recent ACS release - i.e. I'm not aware of any users, nor do I (personally) remember another user mentioning LXC here any time recently.
Cheers Andrija On Wed, 12 Jun 2019 at 15:13, Alejandro Ruiz Bermejo < arbermejo0...@gmail.com> wrote: > Hi this is the full log for one instance cretion with the same error ( > https://pastebin.com/HHKnHi36) > > On Tue, Jun 11, 2019 at 5:10 PM Andrija Panic <andrija.pa...@gmail.com> > wrote: > > > Alejandro, > > > > Please send the whole log on pastebin or similar, this one doesn't > provide > > enough information... (beside the " Found pools matching tags: [] ") > > > > On Tue, 11 Jun 2019 at 17:57, Alejandro Ruiz Bermejo < > > arbermejo0...@gmail.com> wrote: > > > > > ok, so i registered a new template and unset-ed the HVM option and > > > launched a new instance using this themplate. > > > Now the planner can find the host inside the LXC cluster but it seems > > like > > > it can't find now a propper storage pool. I already have everything > > > configured as it appears on the installation guide and configured the > > > secondary and primary storage on the lxc host. I attach and paste here > > the > > > log of the VM creation process > > > > > > root@cloudstack-manager:/home/team# grep -i "unable to" > > > /var/log/cloudstack/management/management-server.log > > > 2019-06-11 11:12:59,917 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > > (API-Job-Executor-19:ctx-23ea94e8 job-51 ctx-06951cdb) (logid:0afee059) > > > com.cloud.exception.InsufficientServerCapacityException: Unable to > > create a > > > deployment for VM[User|i-2-11-VM]Scope=interface > com.cloud.dc.DataCenter; > > > id=1 > > > 2019-06-11 11:12:59,917 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > > (API-Job-Executor-19:ctx-23ea94e8 job-51 ctx-06951cdb) (logid:0afee059) > > > Unable to create a deployment for VM[User|i-2-11-VM] > > > com.cloud.exception.InsufficientServerCapacityException: Unable to > create > > > a deployment for VM[User|i-2-11-VM]Scope=interface > > com.cloud.dc.DataCenter; > > > id=1 > > > 2019-06-11 11:12:59,918 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-19:ctx-23ea94e8 job-51) (logid:0afee059) Complete > async > > > job-51, 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-11-VM]"} > > > 2019-06-11 11:17:33,162 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > > (API-Job-Executor-22:ctx-e044255f job-57 ctx-87af2b3f) (logid:0e16600e) > > > com.cloud.exception.InsufficientServerCapacityException: Unable to > > create a > > > deployment for VM[User|i-2-12-VM]Scope=interface > com.cloud.dc.DataCenter; > > > id=1 > > > 2019-06-11 11:17:33,162 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > > (API-Job-Executor-22:ctx-e044255f job-57 ctx-87af2b3f) (logid:0e16600e) > > > Unable to create a deployment for VM[User|i-2-12-VM] > > > com.cloud.exception.InsufficientServerCapacityException: Unable to > create > > > a deployment for VM[User|i-2-12-VM]Scope=interface > > com.cloud.dc.DataCenter; > > > id=1 > > > 2019-06-11 11:17:33,162 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-22:ctx-e044255f job-57) (logid:0e16600e) Complete > async > > > job-57, 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-12-VM]"} > > > 2019-06-11 11:37:05,302 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > com.cloud.exception.InsufficientServerCapacityException: Unable to > > create a > > > deployment for VM[User|i-2-13-VM]Scope=interface > com.cloud.dc.DataCenter; > > > id=1 > > > 2019-06-11 11:37:05,302 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Unable to create a deployment for VM[User|i-2-13-VM] > > > com.cloud.exception.InsufficientServerCapacityException: Unable to > create > > > a deployment for VM[User|i-2-13-VM]Scope=interface > > com.cloud.dc.DataCenter; > > > id=1 > > > 2019-06-11 11:37:05,302 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Complete > async > > > job-62, 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-13-VM]"} > > > root@cloudstack-manager:/home/team# grep -i "job-62" > > > /var/log/cloudstack/management/management-server.log > > > 2019-06-11 11:37:03,453 INFO [o.a.c.f.j.i.AsyncJobMonitor] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:fb7a7cb5) Add job-62 > > into > > > job monitoring > > > 2019-06-11 11:37:03,459 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (qtp895947612-374:ctx-4c42085e ctx-d0095860) (logid:baf4b65e) submit > > async > > > job-62, details: AsyncJobVO {id:62, userId: 2, accountId: 2, > > instanceType: > > > VirtualMachine, instanceId: 13, cmd: > > > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo: > > > > > > {"httpmethod":"GET","templateid":"f2f98443-3793-452d-8e35-aaf631428c50","ctxAccountId":"2","uuid":"56f3829d-722b-45a1-9084-2576eae34068","cmdEventType":"VM.CREATE","diskofferingid":"3dd93d79-62b0-427c-8c15-1050305eb90e","serviceofferingid":"57675b96-98fa-49a3-9437-24f9dbf3fd90","response":"json","ctxUserId":"2","hypervisor":"LXC","zoneid":"5b03beea-ffdd-45ea-84eb-64110f3ff0d0","ctxStartEventId":"147","id":"13","ctxDetails":"{\"interface > > > > > > com.cloud.vm.VirtualMachine\":\"56f3829d-722b-45a1-9084-2576eae34068\",\"interface > > > > > > com.cloud.offering.ServiceOffering\":\"57675b96-98fa-49a3-9437-24f9dbf3fd90\",\"interface > > > > > > com.cloud.dc.DataCenter\":\"5b03beea-ffdd-45ea-84eb-64110f3ff0d0\",\"interface > > > > > > com.cloud.offering.DiskOffering\":\"3dd93d79-62b0-427c-8c15-1050305eb90e\",\"interface > > > > > > com.cloud.template.VirtualMachineTemplate\":\"f2f98443-3793-452d-8e35-aaf631428c50\"}","_":"1560267550351"}, > > > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, > > > result: null, initMsid: 207380201932, completeMsid: null, lastUpdated: > > > null, lastPolled: null, created: null} > > > 2019-06-11 11:37:03,460 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Executing > > > AsyncJobVO {id:62, userId: 2, accountId: 2, instanceType: > VirtualMachine, > > > instanceId: 13, cmd: > > > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo: > > > > > > {"httpmethod":"GET","templateid":"f2f98443-3793-452d-8e35-aaf631428c50","ctxAccountId":"2","uuid":"56f3829d-722b-45a1-9084-2576eae34068","cmdEventType":"VM.CREATE","diskofferingid":"3dd93d79-62b0-427c-8c15-1050305eb90e","serviceofferingid":"57675b96-98fa-49a3-9437-24f9dbf3fd90","response":"json","ctxUserId":"2","hypervisor":"LXC","zoneid":"5b03beea-ffdd-45ea-84eb-64110f3ff0d0","ctxStartEventId":"147","id":"13","ctxDetails":"{\"interface > > > > > > com.cloud.vm.VirtualMachine\":\"56f3829d-722b-45a1-9084-2576eae34068\",\"interface > > > > > > com.cloud.offering.ServiceOffering\":\"57675b96-98fa-49a3-9437-24f9dbf3fd90\",\"interface > > > > > > com.cloud.dc.DataCenter\":\"5b03beea-ffdd-45ea-84eb-64110f3ff0d0\",\"interface > > > > > > com.cloud.offering.DiskOffering\":\"3dd93d79-62b0-427c-8c15-1050305eb90e\",\"interface > > > > > > com.cloud.template.VirtualMachineTemplate\":\"f2f98443-3793-452d-8e35-aaf631428c50\"}","_":"1560267550351"}, > > > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, > > > result: null, initMsid: 207380201932, completeMsid: null, lastUpdated: > > > null, lastPolled: null, created: null} > > > 2019-06-11 11:37:03,561 DEBUG [c.c.n.NetworkModelImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Service SecurityGroup is not supported in the network id=204 > > > 2019-06-11 11:37:03,562 DEBUG [c.c.n.NetworkModelImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Service SecurityGroup is not supported in the network id=204 > > > 2019-06-11 11:37:03,569 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > DeploymentPlanner allocation algorithm: null > > > 2019-06-11 11:37:03,569 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Trying to allocate a host and storage pools from dc:1, > > > pod:null,cluster:null, requested cpu: 1000, requested ram: 1073741824 > > > 2019-06-11 11:37:03,569 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > Is > > > ROOT volume READY (pool already allocated)?: No > > > 2019-06-11 11:37:03,573 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Deploy avoids pods: [], clusters: [], hosts: [] > > > 2019-06-11 11:37:03,573 DEBUG [c.c.d.FirstFitPlanner] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Searching all possible resources under this Zone: 1 > > > 2019-06-11 11:37:03,573 DEBUG [c.c.d.FirstFitPlanner] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Listing clusters in order of aggregate capacity, that have (atleast one > > > host with) enough CPU and RAM capacity under this Zone: 1 > > > 2019-06-11 11:37:03,575 DEBUG [c.c.d.FirstFitPlanner] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Removing from the clusterId list these clusters from avoid set: [] > > > 2019-06-11 11:37:03,580 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Checking resources in Cluster: 2 under Pod: 1 > > > 2019-06-11 11:37:03,581 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Looking for hosts in dc: 1 > > > pod:1 cluster:2 > > > 2019-06-11 11:37:03,582 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) FirstFitAllocator has 1 > hosts > > to > > > check for allocation: [Host[-4-Routing]] > > > 2019-06-11 11:37:03,585 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Found 1 hosts for allocation > > > after prioritization: [Host[-4-Routing]] > > > 2019-06-11 11:37:03,585 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Looking for speed=1000Mhz, > > > Ram=1024 > > > 2019-06-11 11:37:03,588 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Host: 4 has cpu capability > > > (cpu:8, speed:2666) to support requested CPU: 1 and requested speed: > 1000 > > > 2019-06-11 11:37:03,588 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Checking if host: 4 has > enough > > > capacity for requested CPU: 1000 and requested RAM: 1073741824 , > > > cpuOverprovisioningFactor: 1.0 > > > 2019-06-11 11:37:03,589 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Hosts's actual total CPU: > > 21328 > > > and CPU after applying overprovisioning: 21328 > > > 2019-06-11 11:37:03,589 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Free CPU: 21328 , Requested > > CPU: > > > 1000 > > > 2019-06-11 11:37:03,590 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Free RAM: 15751778304 , > > > Requested RAM: 1073741824 > > > 2019-06-11 11:37:03,590 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Host has enough CPU and RAM > > > available > > > 2019-06-11 11:37:03,590 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) STATS: Can alloc CPU from > > host: > > > 4, used: 0, reserved: 0, actual total: 21328, total with > > overprovisioning: > > > 21328; requested cpu:1000,alloc_from_last_host?:false > > > ,considerReservedCapacity?: true > > > 2019-06-11 11:37:03,590 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) STATS: Can alloc MEM from > > host: > > > 4, used: 0, reserved: 0, total: 15751778304; requested mem: > > > 1073741824,alloc_from_last_host?:false ,considerReservedCapacity?: true > > > 2019-06-11 11:37:03,590 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Found a suitable host, > adding > > to > > > list: 4 > > > 2019-06-11 11:37:03,590 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab > > > FirstFitRoutingAllocator) (logid:5b3ad768) Host Allocator returning 1 > > > suitable hosts > > > 2019-06-11 11:37:03,591 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Checking suitable pools for volume (Id, Type): (22,ROOT) > > > 2019-06-11 11:37:03,591 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > We > > > need to allocate new storagepool for this volume > > > 2019-06-11 11:37:03,592 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Calling StoragePoolAllocators to find suitable pools > > > 2019-06-11 11:37:03,592 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > LocalStoragePoolAllocator trying to find storage pool to fit the vm > > > 2019-06-11 11:37:03,592 DEBUG > > [o.a.c.s.a.ClusterScopeStoragePoolAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > ClusterScopeStoragePoolAllocator looking for storage pool > > > 2019-06-11 11:37:03,592 DEBUG > > [o.a.c.s.a.ClusterScopeStoragePoolAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Looking for pools in dc: 1 pod:1 cluster:2. Disabled pools will be > > > ignored. > > > 2019-06-11 11:37:03,593 DEBUG > > [o.a.c.s.a.ClusterScopeStoragePoolAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Found pools matching tags: [] > > > 2019-06-11 11:37:03,594 DEBUG > > [o.a.c.s.a.ClusterScopeStoragePoolAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > No > > > storage pools available for shared volume allocation, returning > > > 2019-06-11 11:37:03,594 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > ZoneWideStoragePoolAllocator to find storage pool > > > 2019-06-11 11:37:03,595 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > No > > > suitable pools found for volume: Vol[22|vm=13|ROOT] under cluster: 2 > > > 2019-06-11 11:37:03,595 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > No > > > suitable pools found > > > 2019-06-11 11:37:03,595 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > No > > > suitable storagePools found under this Cluster: 2 > > > 2019-06-11 11:37:03,598 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Cluster: 1 has HyperVisorType that does not match the VM, skipping this > > > cluster > > > 2019-06-11 11:37:03,598 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Could not find suitable Deployment Destination for this VM under any > > > clusters, returning. > > > 2019-06-11 11:37:03,598 DEBUG [c.c.d.FirstFitPlanner] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Searching all possible resources under this Zone: 1 > > > 2019-06-11 11:37:03,598 DEBUG [c.c.d.FirstFitPlanner] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Listing clusters in order of aggregate capacity, that have (atleast one > > > host with) enough CPU and RAM capacity under this Zone: 1 > > > 2019-06-11 11:37:03,600 DEBUG [c.c.d.FirstFitPlanner] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Removing from the clusterId list these clusters from avoid set: [1, 2] > > > 2019-06-11 11:37:03,601 DEBUG [c.c.d.FirstFitPlanner] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > No > > > clusters found after removing disabled clusters and clusters in avoid > > list, > > > returning. > > > 2019-06-11 11:37:03,603 DEBUG [c.c.v.UserVmManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Destroying vm VM[User|i-2-13-VM] as it failed to create on Host with > > Id:null > > > 2019-06-11 11:37:03,769 DEBUG [c.c.c.CapacityManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > 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 > > > 2019-06-11 11:37:04,152 DEBUG [c.c.r.ResourceLimitManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Updating resource Type = volume count for Account = 2 Operation = > > > decreasing Amount = 1 > > > 2019-06-11 11:37:04,235 DEBUG [c.c.r.ResourceLimitManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Updating resource Type = primary_storage count for Account = 2 > Operation > > = > > > decreasing Amount = 358010880 > > > 2019-06-11 11:37:04,585 DEBUG [c.c.r.ResourceLimitManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Updating resource Type = volume count for Account = 2 Operation = > > > decreasing Amount = 1 > > > 2019-06-11 11:37:04,710 DEBUG [c.c.r.ResourceLimitManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Updating resource Type = primary_storage count for Account = 2 > Operation > > = > > > decreasing Amount = 5368709120 > > > 2019-06-11 11:37:04,894 WARN [o.a.c.alerts] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > AlertType:: 8 | dataCenterId:: 1 | podId:: null | clusterId:: null | > > > message:: Failed to deploy Vm with Id: 13, on Host with Id: null > > > 2019-06-11 11:37:04,969 DEBUG [c.c.r.ResourceLimitManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Updating resource Type = user_vm count for Account = 2 Operation = > > > decreasing Amount = 1 > > > 2019-06-11 11:37:05,051 DEBUG [c.c.r.ResourceLimitManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Updating resource Type = cpu count for Account = 2 Operation = > decreasing > > > Amount = 1 > > > 2019-06-11 11:37:05,135 DEBUG [c.c.r.ResourceLimitManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Updating resource Type = memory count for Account = 2 Operation = > > > decreasing Amount = 1024 > > > 2019-06-11 11:37:05,302 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > com.cloud.exception.InsufficientServerCapacityException: Unable to > > create a > > > deployment for VM[User|i-2-13-VM]Scope=interface > com.cloud.dc.DataCenter; > > > id=1 > > > 2019-06-11 11:37:05,302 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768) > > > Unable to create a deployment for VM[User|i-2-13-VM] > > > 2019-06-11 11:37:05,302 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Complete > async > > > job-62, 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-13-VM]"} > > > 2019-06-11 11:37:05,303 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Publish > async > > > job-62 complete on message bus > > > 2019-06-11 11:37:05,303 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Wake up jobs > > > related to job-62 > > > 2019-06-11 11:37:05,303 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Update db > > status > > > for job-62 > > > 2019-06-11 11:37:05,304 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Wake up jobs > > > joined with job-62 and disjoin all subjobs created from job- 62 > > > 2019-06-11 11:37:05,386 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Done > executing > > > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin for > job-62 > > > 2019-06-11 11:37:05,386 INFO [o.a.c.f.j.i.AsyncJobMonitor] > > > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Remove > job-62 > > > from job monitoring > > > > > > On Mon, Jun 10, 2019 at 2:51 PM Andrija Panic <andrija.pa...@gmail.com > > > > > wrote: > > > > > >> Interesting lines being: > > >> > > >> FirstFitRoutingAllocator) (logid:0a0b5a30) FirstFitAllocator has 1 > hosts > > >> to > > >> check for allocation: [Host[-4-Routing]] > > >> 2019-06-10 13:40:11,373 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > >> (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 > > >> FirstFitRoutingAllocator) (logid:0a0b5a30) Not considering hosts: > > >> [Host[-4-Routing]] to deploy template: > > >> Tmpl[201-TAR-201-2-ff22b996-a840-3cce-bec2-9ea6ab3081da as they are > not > > >> HVM > > >> enabled > > >> 2019-06-10 13:40:11,374 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > >> (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 > > >> FirstFitRoutingAllocator) (logid:0a0b5a30) Found 0 hosts for > allocation > > >> after prioritization: [] > > >> > > >> i.e. remove the HVM flag from the template and try again (register a > new > > >> template - or go to cloud.vm_templates DB table and set HVM=0 where > your > > >> template=XXXX) > > >> > > >> Andrija > > >> > > >> On Mon, 10 Jun 2019 at 20:20, Alejandro Ruiz Bermejo < > > >> arbermejo0...@gmail.com> wrote: > > >> > > >> > i don't know if its ok sending files over here. In case it is here > is > > >> the > > >> > content of the previous fail i sended > > >> > > > >> > root@cloudstack-manager:/home/team# grep -i "job-41" > > >> > /var/log/cloudstack/management/management-server.log > > >> > 2019-06-10 13:40:11,238 INFO [o.a.c.f.j.i.AsyncJobMonitor] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:5a0455dd) Add > job-41 > > >> into > > >> > job monitoring > > >> > 2019-06-10 13:40:11,246 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Executing > > >> > AsyncJobVO {id:41, userId: 2, accountId: 2, instanceType: > > >> VirtualMachine, > > >> > instanceId: 10, cmd: > > >> > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, > > cmdInfo: > > >> > > > >> > > > >> > > > {"httpmethod":"GET","templateid":"574ce32a-cb06-4f9e-b423-cb2a3e053950","ctxAccountId":"2","uuid":"e5106e36-c36d-49e1-b8e8-4a82ce6fc025","cmdEventType":"VM.CREATE","diskofferingid":"74099b7a-d7bd-44a8-b7da-b01e8e6fa2ed","serviceofferingid":"57675b96-98fa-49a3-9437-24f9dbf3fd90","response":"json","ctxUserId":"2","hypervisor":"LXC","zoneid":"5b03beea-ffdd-45ea-84eb-64110f3ff0d0","ctxStartEventId":"108","id":"10","ctxDetails":"{\"interface > > >> > > > >> > > > >> > > > com.cloud.vm.VirtualMachine\":\"e5106e36-c36d-49e1-b8e8-4a82ce6fc025\",\"interface > > >> > > > >> > > > >> > > > com.cloud.offering.ServiceOffering\":\"57675b96-98fa-49a3-9437-24f9dbf3fd90\",\"interface > > >> > > > >> > > > >> > > > com.cloud.dc.DataCenter\":\"5b03beea-ffdd-45ea-84eb-64110f3ff0d0\",\"interface > > >> > > > >> > > > >> > > > com.cloud.offering.DiskOffering\":\"74099b7a-d7bd-44a8-b7da-b01e8e6fa2ed\",\"interface > > >> > > > >> > > > >> > > > com.cloud.template.VirtualMachineTemplate\":\"574ce32a-cb06-4f9e-b423-cb2a3e053950\"}","_":"1560188536922"}, > > >> > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, > > >> > result: null, initMsid: 207380201932, completeMsid: null, > lastUpdated: > > >> > null, lastPolled: null, created: null} > > >> > 2019-06-10 13:40:11,248 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > >> > (qtp895947612-329:ctx-37027106 ctx-58323b07) (logid:396f8582) submit > > >> async > > >> > job-41, details: AsyncJobVO {id:41, userId: 2, accountId: 2, > > >> instanceType: > > >> > VirtualMachine, instanceId: 10, cmd: > > >> > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, > > cmdInfo: > > >> > > > >> > > > >> > > > {"httpmethod":"GET","templateid":"574ce32a-cb06-4f9e-b423-cb2a3e053950","ctxAccountId":"2","uuid":"e5106e36-c36d-49e1-b8e8-4a82ce6fc025","cmdEventType":"VM.CREATE","diskofferingid":"74099b7a-d7bd-44a8-b7da-b01e8e6fa2ed","serviceofferingid":"57675b96-98fa-49a3-9437-24f9dbf3fd90","response":"json","ctxUserId":"2","hypervisor":"LXC","zoneid":"5b03beea-ffdd-45ea-84eb-64110f3ff0d0","ctxStartEventId":"108","id":"10","ctxDetails":"{\"interface > > >> > > > >> > > > >> > > > com.cloud.vm.VirtualMachine\":\"e5106e36-c36d-49e1-b8e8-4a82ce6fc025\",\"interface > > >> > > > >> > > > >> > > > com.cloud.offering.ServiceOffering\":\"57675b96-98fa-49a3-9437-24f9dbf3fd90\",\"interface > > >> > > > >> > > > >> > > > com.cloud.dc.DataCenter\":\"5b03beea-ffdd-45ea-84eb-64110f3ff0d0\",\"interface > > >> > > > >> > > > >> > > > com.cloud.offering.DiskOffering\":\"74099b7a-d7bd-44a8-b7da-b01e8e6fa2ed\",\"interface > > >> > > > >> > > > >> > > > com.cloud.template.VirtualMachineTemplate\":\"574ce32a-cb06-4f9e-b423-cb2a3e053950\"}","_":"1560188536922"}, > > >> > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, > > >> > result: null, initMsid: 207380201932, completeMsid: null, > lastUpdated: > > >> > null, lastPolled: null, created: null} > > >> > 2019-06-10 13:40:11,347 DEBUG [c.c.n.NetworkModelImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Service SecurityGroup is not supported in the network id=204 > > >> > 2019-06-10 13:40:11,349 DEBUG [c.c.n.NetworkModelImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Service SecurityGroup is not supported in the network id=204 > > >> > 2019-06-10 13:40:11,356 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > DeploymentPlanner allocation algorithm: null > > >> > 2019-06-10 13:40:11,356 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Trying to allocate a host and storage pools from dc:1, > > >> > pod:null,cluster:null, requested cpu: 1000, requested ram: > 1073741824 > > >> > 2019-06-10 13:40:11,356 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> Is > > >> > ROOT volume READY (pool already allocated)?: No > > >> > 2019-06-10 13:40:11,361 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Deploy avoids pods: [], clusters: [], hosts: [] > > >> > 2019-06-10 13:40:11,361 DEBUG [c.c.d.FirstFitPlanner] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Searching all possible resources under this Zone: 1 > > >> > 2019-06-10 13:40:11,362 DEBUG [c.c.d.FirstFitPlanner] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Listing clusters in order of aggregate capacity, that have (atleast > > one > > >> > host with) enough CPU and RAM capacity under this Zone: 1 > > >> > 2019-06-10 13:40:11,364 DEBUG [c.c.d.FirstFitPlanner] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Removing from the clusterId list these clusters from avoid set: [] > > >> > 2019-06-10 13:40:11,371 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Checking resources in Cluster: 2 under Pod: 1 > > >> > 2019-06-10 13:40:11,371 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 > > >> > FirstFitRoutingAllocator) (logid:0a0b5a30) Looking for hosts in dc: > 1 > > >> > pod:1 cluster:2 > > >> > 2019-06-10 13:40:11,372 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 > > >> > FirstFitRoutingAllocator) (logid:0a0b5a30) FirstFitAllocator has 1 > > >> hosts to > > >> > check for allocation: [Host[-4-Routing]] > > >> > 2019-06-10 13:40:11,373 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 > > >> > FirstFitRoutingAllocator) (logid:0a0b5a30) Not considering hosts: > > >> > [Host[-4-Routing]] to deploy template: > > >> > Tmpl[201-TAR-201-2-ff22b996-a840-3cce-bec2-9ea6ab3081da as they are > > not > > >> HVM > > >> > enabled > > >> > 2019-06-10 13:40:11,374 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 > > >> > FirstFitRoutingAllocator) (logid:0a0b5a30) Found 0 hosts for > > allocation > > >> > after prioritization: [] > > >> > 2019-06-10 13:40:11,374 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 > > >> > FirstFitRoutingAllocator) (logid:0a0b5a30) Looking for > speed=1000Mhz, > > >> > Ram=1024 > > >> > 2019-06-10 13:40:11,374 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 > > >> > FirstFitRoutingAllocator) (logid:0a0b5a30) Host Allocator returning > 0 > > >> > suitable hosts > > >> > 2019-06-10 13:40:11,374 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> No > > >> > suitable hosts found > > >> > 2019-06-10 13:40:11,374 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> No > > >> > suitable hosts found under this Cluster: 2 > > >> > 2019-06-10 13:40:11,375 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Cluster: 1 has HyperVisorType that does not match the VM, skipping > > this > > >> > cluster > > >> > 2019-06-10 13:40:11,375 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Could not find suitable Deployment Destination for this VM under any > > >> > clusters, returning. > > >> > 2019-06-10 13:40:11,375 DEBUG [c.c.d.FirstFitPlanner] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Searching all possible resources under this Zone: 1 > > >> > 2019-06-10 13:40:11,376 DEBUG [c.c.d.FirstFitPlanner] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Listing clusters in order of aggregate capacity, that have (atleast > > one > > >> > host with) enough CPU and RAM capacity under this Zone: 1 > > >> > 2019-06-10 13:40:11,378 DEBUG [c.c.d.FirstFitPlanner] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Removing from the clusterId list these clusters from avoid set: [1, > 2] > > >> > 2019-06-10 13:40:11,378 DEBUG [c.c.d.FirstFitPlanner] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> No > > >> > clusters found after removing disabled clusters and clusters in > avoid > > >> list, > > >> > returning. > > >> > 2019-06-10 13:40:11,380 DEBUG [c.c.v.UserVmManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Destroying vm VM[User|i-2-10-VM] as it failed to create on Host with > > >> > Id:null > > >> > 2019-06-10 13:40:11,690 DEBUG [c.c.c.CapacityManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> 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 > > >> > 2019-06-10 13:40:11,964 DEBUG [c.c.r.ResourceLimitManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Updating resource Type = volume count for Account = 2 Operation = > > >> > decreasing Amount = 1 > > >> > 2019-06-10 13:40:12,064 DEBUG [c.c.r.ResourceLimitManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Updating resource Type = primary_storage count for Account = 2 > > >> Operation = > > >> > decreasing Amount = 358010880 > > >> > 2019-06-10 13:40:12,457 DEBUG [c.c.r.ResourceLimitManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Updating resource Type = volume count for Account = 2 Operation = > > >> > decreasing Amount = 1 > > >> > 2019-06-10 13:40:12,598 DEBUG [c.c.r.ResourceLimitManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Updating resource Type = primary_storage count for Account = 2 > > >> Operation = > > >> > decreasing Amount = 21474836480 > > >> > 2019-06-10 13:40:12,707 WARN [o.a.c.alerts] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > AlertType:: 8 | dataCenterId:: 1 | podId:: null | clusterId:: null | > > >> > message:: Failed to deploy Vm with Id: 10, on Host with Id: null > > >> > 2019-06-10 13:40:12,790 DEBUG [c.c.r.ResourceLimitManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Updating resource Type = user_vm count for Account = 2 Operation = > > >> > decreasing Amount = 1 > > >> > 2019-06-10 13:40:12,873 DEBUG [c.c.r.ResourceLimitManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Updating resource Type = cpu count for Account = 2 Operation = > > >> decreasing > > >> > Amount = 1 > > >> > 2019-06-10 13:40:12,957 DEBUG [c.c.r.ResourceLimitManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Updating resource Type = memory count for Account = 2 Operation = > > >> > decreasing Amount = 1024 > > >> > 2019-06-10 13:40:13,124 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > com.cloud.exception.InsufficientServerCapacityException: Unable to > > >> create a > > >> > deployment for VM[User|i-2-10-VM]Scope=interface > > >> com.cloud.dc.DataCenter; > > >> > id=1 > > >> > 2019-06-10 13:40:13,124 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) > > (logid:0a0b5a30) > > >> > Unable to create a deployment for VM[User|i-2-10-VM] > > >> > 2019-06-10 13:40:13,124 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Complete > > >> async > > >> > job-41, 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-10-VM]"} > > >> > 2019-06-10 13:40:13,125 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Publish > > async > > >> > job-41 complete on message bus > > >> > 2019-06-10 13:40:13,125 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Wake up > > jobs > > >> > related to job-41 > > >> > 2019-06-10 13:40:13,125 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Update db > > >> status > > >> > for job-41 > > >> > 2019-06-10 13:40:13,125 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Wake up > > jobs > > >> > joined with job-41 and disjoin all subjobs created from job- 41 > > >> > 2019-06-10 13:40:13,207 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Done > > >> executing > > >> > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin for > > job-41 > > >> > 2019-06-10 13:40:13,207 INFO [o.a.c.f.j.i.AsyncJobMonitor] > > >> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Remove > > job-41 > > >> > from job monitoring > > >> > > > >> > On Mon, Jun 10, 2019 at 1:42 PM Nicolas Vazquez < > > >> > nicolas.vazq...@shapeblue.com> wrote: > > >> > > > >> > > Hi Alejandro, > > >> > > > > >> > > Can you verify if the expected checksum is the correct and i that > > >> case > > >> > > update the checksum column on vm_template table fot that template > > and > > >> > > restart management server? > > >> > > > > >> > > Regards, > > >> > > Nicolas Vazquez > > >> > > ________________________________ > > >> > > From: Alejandro Ruiz Bermejo <arbermejo0...@gmail.com> > > >> > > Sent: Monday, June 10, 2019 12:38:52 PM > > >> > > To: users@cloudstack.apache.org > > >> > > Subject: launch instance error > > >> > > > > >> > > Hi, I'm working with Cloudstack 4.11.2.0 > > >> > > > > >> > > This is my environment: > > >> > > 1 Zone > > >> > > 1 Pod > > >> > > 2 Clusters (LXC and KVM) > > >> > > 2 Hosts (one in each cluster) > > >> > > > > >> > > i can launch perfectly VMs on the KVM cluster but when i'm trying > to > > >> > launch > > >> > > a new VM with an LXC template i'm getting this error: > > >> > > > > >> > > 2019-06-10 11:24:28,961 INFO [a.c.c.a.ApiServer] > > >> > > (qtp895947612-18:ctx-e1a5bd5e ctx-bc704f1b) (logid:2635d81d) > > (userId=2 > > >> > > accountId=2 sessionId=node0a04x8pj44gz8mf2hb5ikizk20) 10.8.2.116 > -- > > >> GET > > >> > > command=listAlerts&response=json&page=1&pageSize=4&_=1560180395194 > > 200 > > >> > > > > >> > > > > >> > > > >> > > > {"listalertsresponse":{"count":16,"alert":[{"id":"c896ae0a-764b-4976-9dc1-7868f9f61e3c","type":8,"name":"ALERT.USERVM","description":"Failed > > >> > > to deploy Vm with Id: 5, on Host with Id: > > >> > > > > >> > > > > >> > > > >> > > > null","sent":"2019-06-10T11:15:19-0400"},{"id":"42988261-9238-430f-af54-1582073b35d0","type":8,"name":"ALERT.USERVM","description":"Failed > > >> > > to deploy Vm with Id: 4, on Host with Id: > > >> > > > > >> > > > > >> > > > >> > > > null","sent":"2019-06-10T10:36:40-0400"},{"id":"fc89bba6-9890-4aa7-b57a-3dc3a2e14643","type":8,"name":"ALERT.USERVM","description":"Failed > > >> > > to deploy Vm with Id: 3, on Host with Id: > > >> > > > > >> > > > > >> > > > >> > > > null","sent":"2019-06-10T10:31:05-0400"},{"id":"e3ab7e4b-5ce7-4c50-893e-0432c23f684f","type":28,"name":"ALERT.UPLOAD.FAILED","description":"Failed > > >> > > to register template: 59eaea2c-8883-11e9-bc81-003048d2c1cc with > > error: > > >> > > Failed post download script: checksum > > >> > > \"{MD5}292bfea2667a3a23a71d42d53d68b8fc\" didn't match the given > > >> value, > > >> > > > > >> > > > > >> > > > >> > > > \"{MD5}c2c4fa2d0978121c7977db571f132d6e\"","sent":"2019-06-10T10:28:19-0400"}]}} > > >> > > > > >> > > I'm seeing two errors here one is the Host ID: * Host with Id: > null* > > >> > > And the other one is a checksum verification > > >> > > > > >> > > When i created the LXC template i had to change the Download > > >> Keyserver > > >> > for > > >> > > the lxc-create -t download step so idk if this is causing the > > checksum > > >> > > error > > >> > > > > >> > > any help with this would be great > > >> > > > > >> > > nicolas.vazq...@shapeblue.com > > >> > > www.shapeblue.com > > >> > > Amadeus House, Floral Street, London WC2E 9DPUK > > >> > > @shapeblue > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > >> > > >> > > >> -- > > >> > > >> Andrija Panić > > >> > > > > > > > -- > > > > Andrija Panić > > > -- Andrija Panić
