You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/30 23:54:20 UTC

[jira] [Commented] (CLOUDSTACK-2771) Unable to create guest VM in basic zone: Zone is dedicated

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670789#comment-13670789 ] 

ASF subversion and git services commented on CLOUDSTACK-2771:
-------------------------------------------------------------

Commit 7296cca9ac1121b962739a474f9d9ce0bd162fb6 in branch refs/heads/master from Prachi Damle <pr...@cloud.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7296cca ]

CLOUDSTACK-2771: Unable to create guest VM in basic zone: Zone is dedicated

Changes:
- Check the domain of the dedicated zone

                
> Unable to create guest VM in basic zone: Zone is dedicated
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-2771
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2771
>             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
>         Environment: 4.2.0, vmware setup (haven't checked if this issue is seen in non-vmware cloudstack deployments).
>            Reporter: Venkata Siva Vijayendra Bhamidipati
>             Fix For: 4.2.0
>
>
> 1) Create a basic zone in cloudstack using the zone wizard, with hypervisor type set to vmware. Select "DefaultSharedNetworkOffering" as the network offering.
> 2) Attempt to create a guest VM using the instance wizard. The operation fails with the following exception seen in the logs:
> WARN  [apache.cloudstack.alerts] (Job-Executor-9:job-9)  alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null
> ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-9) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM. Zone bzone1 is dedicated.
>         at com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:454)
>         at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:213)
>         at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186)
>         at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
>         at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3268)
>         at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2807)
>         at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2793)
>         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:1146)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:679)

--
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