sbrueseke opened a new issue, #8077:
URL: https://github.com/apache/cloudstack/issues/8077
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
UI, Log
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18.1.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When a specified host does not have enough free memory capacity the logfile
and UI shows the following error message:
Cannot deploy the VM to specified host 10; host has cpu capability? true,
host has capacity? false
Which is a little bit irritating, because memory as a reason is not
mentioned.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
deploy instances as root and specify host in deployment wizard. When host
does not have enough free available memory, you see the error in UI and logfile.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
error message should mention the root reason for not be able to deploy vm.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Logfile looks like this and UI shows error message from logfile:
2023-10-11 15:52:46,928 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f)
Destination Host to deploy the VM is specified, specifying a deployment plan to
de
ploy the VM
2023-10-11 15:52:46,939 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f) Host:
10 has cpu capability (cpu:56, speed:2400) to support requested CPU: 4 and
requested speed: 2000
2023-10-11 15:52:46,940 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f)
Checking if host: 10 has enough capacity for requested CPU: 8000 and requested
RAM: (8.00 GB) 8589934592 , cpuOverprovisioningFactor: 4.0
2023-10-11 15:52:46,945 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f)
Hosts's actual total CPU: 134400 and CPU after applying overprovisioning: 537600
2023-10-11 15:52:46,945 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f)
considerReservedCapacity isfalse , not considering reserved capacity for
calculating free capacity
2023-10-11 15:52:46,945 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f) Free
CPU: 160100 , Requested CPU: 8000
2023-10-11 15:52:46,945 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f) Free
RAM: (7.03 GB) 7550763008 , Requested RAM: (8.00 GB) 8589934592
2023-10-11 15:52:46,945 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f)
STATS: Failed to alloc resource from host: 10, reservedCpu: 0, used cpu:
377500, requested cpu: 8000, actual total cpu: 134400, total cpu with
overprovisioning: 537600, reservedMem: (0 bytes) 0, used Mem: (369.75 GB)
397016039424, requested mem: (8.00 GB) 8589934592, total Mem:(376.78 GB)
404566802432 ,considerReservedCapacity?: false
2023-10-11 15:52:46,946 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f) Host
does not have enough RAM available, cannot allocate to this host.
2023-10-11 15:52:46,946 INFO [c.c.v.UserVmManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f)
Cannot deploy the VM to specified host 10; host has cpu capability? true, host
has capacity? false
2023-10-11 15:52:46,952 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f)
Destroying vm VM instance
{"id":242,"instanceName":"i-2-242-VM","type":"User","uuid":"0ac79f1a-16c5-42c0-8448-a872e55ee3ca"}
as it failed to create on Host with Id:10
2023-10-11 15:52:46,981 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f) VM
instance
{"id":242,"instanceName":"i-2-242-VM","type":"User","uuid":"0ac79f1a-16c5-42c0-8448-a872e55ee3ca"}
state transited from [Stopped] to [Error] with event [OperationFailedToError].
VM's original host: null, new host: null, host before state transition: null
2023-10-11 15:52:47,017 DEBUG [c.c.s.d.VolumeDaoImpl]
(API-Job-Executor-50:ctx-98e0cc75 job-1563 ctx-89e70556) (logid:cc26398f)
Removing volume 248 from DB
~~~
--
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: commits-unsubscr...@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
