You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kiran Koneti (JIRA)" <ji...@apache.org> on 2013/07/09 12:13:48 UTC
[jira] [Closed] (CLOUDSTACK-2662) Preferred implicit dedication
fails with insufficient capacity even if shared hosts are available.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Koneti closed CLOUDSTACK-2662.
------------------------------------
Closing the issue as it is not observed in the Latest Build.
> Preferred implicit dedication fails with insufficient capacity even if shared hosts are available.
> --------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2662
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2662
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Kiran Koneti
> Assignee: Rajesh Battala
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Below are the steps followed :
> 1)Created a Xen Advanced Zone setup with one cluster and hosts.
> 2)The host1 has the system VM's deployed and a VM with the root domain.
> 3)Then created two accounts kiran and kiran2 respectively.
> 4)Was able to deploy VM's using the preferred and strict implicit dedication for the Account kiran.
> 5)Then tried to deploy a VM fro the account kiran2 using the preferred implicit service offering.
> 6)The VM deployment fails saying insufficient resources even we have the host 1 in the shared state.
> the below error message is observed
> "2013-05-24 16:15:09,565 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-22) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[U ser|win832pref2]Scope=interface com.cloud.dc.DataCenter; id=1
> 2013-05-24 16:15:09,565 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-22) Unable to create a deployment for VM[User|win832pref2]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|win832pref2]Scope=interface com.cloud.dc.DataCenter; id=1
> at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:212)
> at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3206)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2745)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2731)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)"
> The op_host_planner_reservation shows the host dedication details as below:
> mysql> select * from op_host_planner_reservation;
> +----+----------------+--------+------------+---------+----------------+
> | id | data_center_id | pod_id | cluster_id | host_id | resource_usage |
> +----+----------------+--------+------------+---------+----------------+
> | 1 | 1 | 1 | 1 | 1 | Shared |
> | 2 | 1 | 1 | 1 | 5 | Dedicated |
> +----+----------------+--------+------------+---------+----------------+
> 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