[
https://issues.apache.org/jira/browse/CLOUDSTACK-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608081#comment-14608081
]
Martin Emrich commented on CLOUDSTACK-2344:
-------------------------------------------
I had this effect here just now with ACS 4.4.3: Cluster with two XenServers
(one is completely full, the other is ca. 60% full memory-wise). Instead of
starting the VM on the second host, I just get "Unable to create a deployment"
error and this error message.
{code}
2015-06-30 10:46:39,135 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-104:ctx-e46c44d8) Unable to start VM(i-11-495-VM) on
host(564da24e-adad-45e9-9762-ace35f273632) due to Task failed! Task record:
uuid: 7afa6bf7-2808-10fe-96d7-d06b699a3205
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Tue Jun 30 10:46:37 CEST 2015
finished: Tue Jun 30 10:46:38 CEST 2015
status: failure
residentOn: com.xensource.xenapi.Host@cf13d8bd
progress: 1.0
type: <none/>
result:
errorInfo: [HOST_NOT_ENOUGH_FREE_MEMORY, 4447010816, 3783258112]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
{code}
{code}
2015-06-30 10:46:39,189 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-1751fe27) Seq 335-2451647047149846459: Response Received:
2015-06-30 10:46:39,189 DEBUG [c.c.a.t.Request] (DirectAgent-18:ctx-1751fe27)
Seq 335-2451647047149846459: Processing: { Ans: , MgmtId: 194080961590576,
via: 335, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.StopAnswer":{"result":true,"de
tails":"VM does not exist","wait":0}}] }
2015-06-30 10:46:39,189 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Seq
335-2451647047149846459: Received: { Ans: , MgmtId: 194080961590576, via: 335,
Ver: v1, Flags: 10, { StopAnswer } }
2015-06-30 10:46:39,192 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Changing
active number of nics for network id=208 on -1
2015-06-30 10:46:39,193 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669)
Successfully released network resources for the vm VM[User|i-11-495-VM]
2015-06-30 10:46:39,193 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669)
Successfully cleanued up resources for the vm VM[User|i-11-495-VM] in Starting
state
2015-06-30 10:46:39,194 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Root
volume is ready, need to place VM in volume's cluster
2015-06-30 10:46:39,208 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Deploy
avoids pods: [], clusters: [], hosts: [335]
2015-06-30 10:46:39,208 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669)
DeploymentPlanner allocation algorithm:
com.cloud.deploy.FirstFitPlanner@349b99ac
2015-06-30 10:46:39,208 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Trying to
allocate a host and storage pools from dc:1, pod:1,cluster:3, requested cpu:
3000, request
ed ram: 4294967296
2015-06-30 10:46:39,208 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Is ROOT
volume READY (pool already allocated)?: Yes
2015-06-30 10:46:39,208 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669)
DeploymentPlan has host_id specified, choosing this host and making no checks
on this host: 335
2015-06-30 10:46:39,209 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) The
specified host is in avoid set
2015-06-30 10:46:39,209 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Cannnot
deploy to specified host, returning.
2015-06-30 10:46:39,212 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) VM state
transitted from :Starting to Stopped with event: OperationFailedvm's original
host id: null new host
id: null host id before state transition: 335
2015-06-30 10:46:39,214 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Hosts's
actual total CPU: 57600 and CPU after applying overprovisioning: 460800
2015-06-30 10:46:39,214 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Hosts's
actual total RAM: 128831420928 and RAM after applying overprovisioning:
128831422464
2015-06-30 10:46:39,214 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) release
cpu from host: 335, old used: 147000,reserved: 0, actual total: 57600, total
with overprovisioning: 46
0800; new used: 144000,reserved:0; movedfromreserved:
false,moveToReserveredfalse
2015-06-30 10:46:39,214 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) release
mem from host: 335, old used: 127003525120,reserved: 0, total: 128831422464;
new used: 122708557824,re
served:0; movedfromreserved: false,moveToReserveredfalse
2015-06-30 10:46:39,219 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Invocation
exception, caused by: com.cloud.exception.InsufficientServerCapacityException:
Unable to create a
deployment for VM[User|i-11-495-VM]Scope=interface com.cloud.dc.DataCenter;
id=1
2015-06-30 10:46:39,225 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996 ctx-f10a3669) Rethrow
exception com.cloud.exception.InsufficientServerCapacityException: Unable to
create a deployment for
VM[User|i-11-495-VM]Scope=interface com.cloud.dc.DataCenter; id=1
2015-06-30 10:46:39,225 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgentCronJob-341:ctx-4469565d) Ping from 323(esc-fra1-xn002)
2015-06-30 10:46:39,225 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 495, job origin: 43995
2015-06-30 10:46:39,225 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-341:ctx-4469565d) Process host VM state report from ping
process. host: 323
2015-06-30 10:46:39,225 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-30:ctx-f38cad48 job-43995/job-43996) Unable to complete
AsyncJobVO {id:43996, userId: 11, accountId: 11, instanceType: null,
instanceId: null, cmd: com.cloud.vm
.VmWorkStart, cmdInfo:
rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAAAAAAAAAALAAAAAAAAAAsAAAAAAAAB73QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAAAAAAAAAXBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAANzcQB-AAgAAAAAAAABT3BwcHNxAH4ACAAAAAAAAAABcHNyABFqYXZhLnV0aWwuSGFzaE1hcAUH2sHDFmDRAwACRgAKbG9hZEZhY3RvckkACXRocmVzaG9sZHhwP0AAAAAAAAx3CAAAABAAAAABdAAKVm1QYXNzd29yZHQAHHJPMEFCWFFBRG5OaGRtVmtYM0JoYzNOM2IzSmt4cA,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 194080961590576, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Tue Jun 30 10:46:22 CEST 2015}, job origin:43995
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|i-11-495-VM]Scope=interface com.cloud.dc.DataCenter; id=1
{code}
> not enough free memory on one host of the cluster
> -------------------------------------------------
>
> Key: CLOUDSTACK-2344
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2344
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: XenServer
> Affects Versions: 4.0.1, 4.1.0, 4.2.0
> Reporter: Nikita Gubenko
> Priority: Minor
>
> Hi
> I'm testing some overprovisioning cases. I have two XenServer hosts with lots
> of VMs on each.
> When I try to upgrade resources on the VM on the host that doesn't have
> enough free memory for it and try to start it I get
> Task failed! Task record: uuid: 0582f281-5a54-27cd-ba23-a4edf60312f4
> nameLabel: Async.VM.start_on
> nameDescription:
> allowedOperations: []
> currentOperations: {}
> created: Thu Apr 25 00:29:34 MSK 2013
> finished: Thu Apr 25 00:29:34 MSK 2013
> status: failure
> residentOn: com.xensource.xenapi.Host@234582ee
> progress: 1.0
> type: <none/>
> result:
> errorInfo: [HOST_NOT_ENOUGH_FREE_MEMORY, 8659140608, 6721728512]
> otherConfig: {}
> subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
> This is normal behavior, but CS doesn't try to start this VM on the second
> host of the cluster which has enough free memory. OfferHA option is enabled.
> I think this should be fixed, because there is no balanced VM distribution
> within a cluster, so this situation can occur.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
