[ https://issues.apache.org/jira/browse/CLOUDSTACK-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devdeep Singh resolved CLOUDSTACK-2666. --------------------------------------- Resolution: Fixed Assignee: Devdeep Singh UI was passing the wrong parameter string for 'preferred' mode. Because of that, the planner used to default to 'Strict' mode. The issue was fixed in commit 8b9d6d81a229441cc5a9e3c0bf61e81de9ea6c5d. > Host is getting dedicated to a Account even when preferred implicit > dedication is used. > --------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-2666 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2666 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Reporter: Kiran Koneti > Assignee: Devdeep Singh > Priority: Blocker > > 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)Deployed VM using the preferred 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 > The error message is as below > "2013-05-24 17:49:33,285 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-26) > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[User|prefacc2]Scope=interface com.cloud.dc.DataCenter; id=1 > 2013-05-24 17:49:33,287 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-26) > Unable to create a deployment for VM[User|prefacc2] > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[User|prefacc2]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)" > Ideally saying the host should not be dedicated to the account kiran but this > is getting dedicated which is causing the vm creation failure for the account > kiran2. > The db shows the host in dedicated state. > "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