Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 12 Jul 2013 09:23:48 +0000 (UTC)
From: "Abhinandan Prateek (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12639085.1364301623027.39032.1373621028084@arcas>
In-Reply-To: <JIRA.12639085.1364301623027@arcas>
References: <JIRA.12639085.1364301623027@arcas>
Subject: [jira] [Assigned] (CLOUDSTACK-1809) Actual capacity availble for vm
 deployement in vmware cluster is less than what Dashboard shows
 (total_capacity in op_host_capacity  table)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhinandan Prateek reassigned CLOUDSTACK-1809:
----------------------------------------------

    Assignee: Nitin Mehta

Can you comment what could be wrong and that it needs to be assigned to the VMWare specialist ?
                
> Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity  table)
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1809
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1809
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.2.0
>         Environment: vmware
>            Reporter: prashant kumar mishra
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: DB_Logs.rar, screenshot-1.jpg, screenshot-2.jpg
>
>
> ->For vmware cluster(with only  one host)  vcenter shows total capacity of cluster is (Memory 13431 MB, CPU 7752MHz) which is available for vm deployment and cloud stack shows (Memory 15.99 GB, CPU  9572)  .
> ->Due to this calculation difference CS allocator shows capacity is available on host but   vm deployment fails  with run time error 
> "2013-06-13 12:23:01,945 WARN  [vmware.resource.VmwareResource] (DirectAgent-141:10.147.40.7) StartCommand failed due to Exception: java.lang.RuntimeException
> Message: The available CPU resources in the parent resource pool are insufficient for the operation.
> java.lang.RuntimeException: The available CPU resources in the parent resource pool are insufficient for the operation.
> "   
> DB
> -----
> mysql> select *from op_host_capacity where capacity_type in (0,1)\G;
> *************************** 1. row ***************************
>                id: 1
>           host_id: 1
>    data_center_id: 1
>            pod_id: 1
>        cluster_id: 1
>     used_capacity: 6039797760
> reserved_capacity: 0
>    total_capacity: 17169539072
>     capacity_type: 0
>    capacity_state: Enabled
>       update_time: 2013-06-13 15:29:33
>           created: 2013-06-05 16:05:51
> *************************** 2. row ***************************
>                id: 2
>           host_id: 1
>    data_center_id: 1
>            pod_id: 1
>        cluster_id: 1
>     used_capacity: 7700
> reserved_capacity: 0
>    total_capacity: 9572
>     capacity_type: 1
>    capacity_state: Enabled
>       update_time: 2013-06-13 15:29:33
>           created: 2013-06-05 16:05:51
> 2 rows in set (0.00 sec)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira