You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Jevgeni Zolotarjov (JIRA)" <ji...@apache.org> on 2017/10/23 08:24:00 UTC
[jira] [Created] (CLOUDSTACK-10116) Unable to create a deployment
for VM: better error reportintg for InsufficientServerCapacityException
Jevgeni Zolotarjov created CLOUDSTACK-10116:
-----------------------------------------------
Summary: Unable to create a deployment for VM: better error reportintg for InsufficientServerCapacityException
Key: CLOUDSTACK-10116
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10116
Project: CloudStack
Issue Type: Improvement
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.10.0.0
Reporter: Jevgeni Zolotarjov
An attempt to create new instance failed with an error:
*Unable to create a deployment for VM*
For understanding the problem, I had to
1. analyze the logs,
2. Locate InsufficientServerCapacityException and understand what it means.
2. multiply [service offering core count] x [service offering MHz] and
3. check it against the remainder from the indicator on the dashboard.
4. consider cpu.overprovisioning.factor
Expected:
The clear error for the user about the real reason of the problem is good solution for this problem.
The text could be: "Insufficient CPU resources to create new VM. You can try increasing cpu.overprovisioning.factor system variable. Be careful with this, cause it might impact performance of your other VMs."
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)