fangyi1008 opened a new issue, #7053:
URL: https://github.com/apache/cloudstack/issues/7053
2023-01-05 10:36:33,001 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Destination Host to deploy the VM is specified, specifying a deployment plan to
deploy the VM
2023-01-05 10:36:33,004 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Host:
1 has cpu capability (cpu:128, speed:2000000) to support requested CPU: 1 and
requested speed: 1000
2023-01-05 10:36:33,004 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Checking if host: 1 has enough capacity for requested CPU: 1000 and requested
RAM: (1.00 GB) 1073741824 , cpuOverprovisioningFactor: 1.0
2023-01-05 10:36:33,005 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Hosts's actual total CPU: 256000000 and CPU after applying overprovisioning:
256000000
2023-01-05 10:36:33,005 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
considerReservedCapacity isfalse , not considering reserved capacity for
calculating free capacity
2023-01-05 10:36:33,005 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Free
CPU: 255999000 , Requested CPU: 1000
2023-01-05 10:36:33,006 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Free
RAM: (501.02 GB) 537961562112 , Requested RAM: (1.00 GB) 1073741824
2023-01-05 10:36:33,006 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Host
has enough CPU and RAM available
2023-01-05 10:36:33,006 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) STATS:
Can alloc CPU from host: 1, used: 1000, reserved: 0, actual total: 256000000,
total with overprovisioning: 256000000; requested cpu:
1000,alloc_from_last_host?:false ,considerReservedCapacity?: false2023-01-05
10:36:33,006 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) STATS:
Can alloc MEM from host: 1, used: (1.50 GB) 1610612736, reserved: (0 bytes) 0,
total: (502.52 GB) 539572174848; requested mem: (1.00
GB) 1073741824, alloc_from_last_host?: false , considerReservedCapacity?:
false2023-01-05 10:36:33,009 DEBUG [c.c.a.ApiServlet]
(qtp1747352992-285:ctx-38d5a57c) (logid:e0539ea9) ===START=== 192.168.0.102 --
GET
jobId=8270895e-bb89-41f6-8f67-3c2f33a4b30d&command=queryAsyncJobResult&response=json
2023-01-05 10:36:33,014 DEBUG [c.c.a.ApiServer]
(qtp1747352992-285:ctx-38d5a57c ctx-b4ed1e0d) (logid:e0539ea9) CIDRs from which
account 'Acct[2217c707-8817-11ed-9cb1-04421a1ae40d-admin] -- Account {"id": 2,
"name": "admin", "uuid": "2217c707-8817-11ed-9cb1-04421a1ae40d"
}' is allowed to perform API calls: 0.0.0.0/0,::/02023-01-05 10:36:33,015
DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-18:ctx-41c893ef
job-305 ctx-e4d8c684) (logid:8270895e) Adding pods to avoid lists for
non-explicit VM deployment: []
2023-01-05 10:36:33,015 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Adding
clusters to avoid lists for non-explicit VM deployment: []
2023-01-05 10:36:33,015 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Adding
hosts to avoid lists for non-explicit VM deployment: []
2023-01-05 10:36:33,015 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
DeploymentPlanner allocation algorithm: null
2023-01-05 10:36:33,015 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Trying
to allocate a host and storage pools from dc:1, pod:1,cluster:1, requested cpu:
1000, requested ram: (1.00 GB) 1073741824
2023-01-05 10:36:33,015 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Is
ROOT volume READY (pool already allocated)?: No
2023-01-05 10:36:33,019 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
DeploymentPlan has host_id specified, choosing this host and making no checks
on this host: 1
2023-01-05 10:36:33,020 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Looking for suitable pools for this host under zone: 1, pod: 1, cluster: 1
2023-01-05 10:36:33,022 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Checking suitable pools for volume (Id, Type): (70,ROOT)
2023-01-05 10:36:33,022 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) We
need to allocate new storagepool for this volume
2023-01-05 10:36:33,023 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Calling StoragePoolAllocators to find suitable pools
2023-01-05 10:36:33,024 DEBUG [c.c.a.ApiServlet]
(qtp1747352992-285:ctx-38d5a57c ctx-b4ed1e0d) (logid:e0539ea9) ===END===
192.168.0.102 -- GET
jobId=8270895e-bb89-41f6-8f67-3c2f33a4b30d&command=queryAsyncJobResult&response=json
2023-01-05 10:36:33,027 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) No
suitable pools found for volume: Vol[70|vm=90|ROOT] under cluster: 1
2023-01-05 10:36:33,027 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) No
suitable pools found
2023-01-05 10:36:33,027 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) Cannot
deploy to specified host, returning.
2023-01-05 10:36:33,028 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Destroying vm VM instance {id: "90", name: "i-2-90-VM", uuid:
"27615bc8-9d9f-4469-a2d7-215de3bd6a31", type="User"} as it failed to create on
Host with Id:12023-01-05 10:36:33,045 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) VM
instance {id: "90", name: "i-2-90-VM", uuid:
"27615bc8-9d9f-4469-a2d7-215de3bd6a31", type="User"} state transited from
[Stopped] to [Err
or] with event [OperationFailedToError]. VM's original host: null, new host:
null, host before state transition: null2023-01-05 10:36:33,059 DEBUG
[c.c.r.ResourceLimitManagerImpl] (API-Job-Executor-18:ctx-41c893ef job-305
ctx-e4d8c684) (logid:8270895e) Updating resource Type = volume count for
Account = 2 Operation = decreasing Amount = 1
2023-01-05 10:36:33,069 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Updating resource Type = primary_storage count for Account = 2 Operation =
decreasing Amount = (20.00 GB) 21474836480
2023-01-05 10:36:33,085 WARN [c.c.a.AlertManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
alertType=[8] dataCenterId=[1] podId=[null] clusterId=[null] message=[Failed to
deploy Vm with Id: 90, on Host with Id: 1].
2023-01-05 10:36:33,091 WARN [c.c.a.AlertManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e) No
recipients set in global setting 'alert.email.addresses', skipping sending
alert with subject [Failed to deploy Vm with Id: 90, on Host wit
h Id: 1] and content [Failed to deploy Vm with Id: 90, on Host with Id:
1].2023-01-05 10:36:33,092 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Updating resource Type = user_vm count for Account = 2 Operation = decreasing
Amount = 1
2023-01-05 10:36:33,100 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Updating resource Type = cpu count for Account = 2 Operation = decreasing
Amount = 1
2023-01-05 10:36:33,105 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
Updating resource Type = memory count for Account = 2 Operation = decreasing
Amount = 1024
2023-01-05 10:36:33,118 INFO [o.a.c.a.c.u.v.DeployVMCmd]
(API-Job-Executor-18:ctx-41c893ef job-305 ctx-e4d8c684) (logid:8270895e)
com.cloud.exception.InsufficientServerCapacityException: No destination found
for a deployment for VM instance {id: "90", name: "i-2-90-VM"
, uuid: "27615bc8-9d9f-4469-a2d7-215de3bd6a31", type="User"}Scope=interface
com.cloud.dc.DataCenter; id=12023-01-05 10:36:33,120 INFO
[o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-18:ctx-41c893ef job-305
ctx-e4d8c684) (logid:8270895e) No destination found for a deployment for VM
instance {id: "90", name: "i-2-90-VM", uuid:
"27615bc8-9d9f-4469-a2d7-215de3bd6a31", type="Use
r"}com.cloud.exception.InsufficientServerCapacityException: No destination
found for a deployment for VM instance {id: "90", name: "i-2-90-VM", uuid:
"27615bc8-9d9f-4469-a2d7-215de3bd6a31", type="User"}Scope=interface
com.cloud.dc.DataCenter; id=1
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:225)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:202)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:5310)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:5161)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4788)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4777)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:52)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
at com.sun.proxy.$Proxy180.startVirtualMachine(Unknown Source)
at
org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:714)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:163)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:106)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
2023-01-05 10:36:33,129 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-18:ctx-41c893ef job-305) (logid:8270895e) Remove job-305 from
job monitoring
2023-01-05 10:36:33,353 DEBUG [c.c.a.ApiServlet]
(qtp1747352992-514:ctx-bc1de5cb) (logid:9774c341) ===START=== 192.168.0.102 --
GET
resourceids=8f55ef53-d2bf-4906-b115-fe527160f7aa&resourcetype=template&command=listResourceIcon&response=json
2023-01-05 10:36:33,354 DEBUG [c.c.a.ApiServlet]
(qtp1747352992-458:ctx-9e8902ce) (logid:39d7b02f) ===START=== 192.168.0.102 --
GET
listall=true&page=1&pagesize=20&showIcon=true&command=listVirtualMachinesMetrics&response=json
2023-01-05 10:36:33,357 DEBUG [c.c.a.ApiServer]
(qtp1747352992-514:ctx-bc1de5cb ctx-1c2851ae) (logid:9774c341) CIDRs from which
account 'Acct[2217c707-8817-11ed-9cb1-04421a1ae40d-admin] -- Account {"id": 2,
"name": "admin", "uuid": "2217c707-8817-11ed-9cb1-04421a1ae40d"
}' is allowed to perform API calls: 0.0.0.0/0,::/02023-01-05 10:36:33,358
DEBUG [c.c.a.ApiServer] (qtp1747352992-458:ctx-9e8902ce ctx-7f77c6f8)
(logid:39d7b02f) CIDRs from which account
'Acct[2217c707-8817-11ed-9cb1-04421a1ae40d-admin] -- Account {"id": 2, "name":
"admin", "uuid": "2217c707-8817-11ed-9cb1-04421a1ae40d"
}' is allowed to perform API calls: 0.0.0.0/0,::/0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
