You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinav Roy (JIRA)" <ji...@apache.org> on 2013/12/30 13:32:51 UTC
[jira] [Closed] (CLOUDSTACK-5564) [Hyper-V] When we have multiple
hosts in a cluster then the vms are always created on only Host. It says
that other hosts can not access the storage pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinav Roy closed CLOUDSTACK-5564.
-----------------------------------
Closing the issue after fix validation
> [Hyper-V] When we have multiple hosts in a cluster then the vms are always created on only Host. It says that other hosts can not access the storage pool
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5564
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5564
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Hypervisor Controller, Management Server, Storage Controller
> Affects Versions: 4.3.0
> Environment: 4.3, Hyper-V
> Reporter: Abhinav Roy
> Assignee: Devdeep Singh
> Priority: Blocker
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.3.0
>
>
> Steps :
> ================================
> 1. Deploy a CS setup with a single hyperv host, ex host1
> 2. Deploy some vms on the setup.
> 3. Now add another hyperv host , host2 in the same cluster
> 4. Deploy VMs using UI on Host 2
> 5. Deploy VMs using API on host2
> Expected behaviour :
> ==============================
> The VMs shoould be created on host2 in step4 and 5
> Observed behaviour :
> ============================
> In step 4 the VMs get created on Host1. and when we fire the API in step5,
> http://10.102.192.125:8096/client/api?command=deployVirtualMachine&templateid=202&zoneid=1&serviceofferingid=1&networkids=204&hostid=4&account=admin&domainid=1
> following error is seen in the logs :
> 2013-12-19 16:22:08,001 DEBUG [c.c.v.UserVmManagerImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Allocating in the DB for vm
> 2013-12-19 16:22:08,009 DEBUG [c.c.v.VirtualMachineManagerImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Allocating entries for VM: VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]
> 2013-12-19 16:22:08,010 DEBUG [c.c.v.VirtualMachineManagerImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Allocating nics for VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]
> 2013-12-19 16:22:08,010 DEBUG [o.a.c.e.o.NetworkOrchestrator] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Allocating nic for vm VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9] in network Ntwk[204|Guest|8] with requested profile NicProfile[0-0-null-null-null
> 2013-12-19 16:22:08,021 DEBUG [c.c.n.NetworkModelImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Service SecurityGroup is not supported in the network id=204
> 2013-12-19 16:22:08,022 DEBUG [c.c.v.VirtualMachineManagerImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Allocating disks for VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]
> 2013-12-19 16:22:08,030 DEBUG [c.c.v.VirtualMachineManagerImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Allocation completed for VM: VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]
> 2013-12-19 16:22:08,030 DEBUG [c.c.v.UserVmManagerImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Successfully allocated DB entry for VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]
> 2013-12-19 16:22:08,048 DEBUG [c.c.n.NetworkModelImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Service SecurityGroup is not supported in the network id=204
> 2013-12-19 16:22:08,051 DEBUG [c.c.n.NetworkModelImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) Service SecurityGroup is not supported in the network id=204
> 2013-12-19 16:22:08,071 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (ApiServer-4:ctx-2f46d2cd ctx-2b3b4192) submit async job-82, details: AsyncJobVO {id:82, userId: 1, accountId: 1, instanceType: VirtualMachine, instanceId: 26, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: {"serviceofferingid":"1","cmdEventType":"VM.CREATE","ctxUserId":"1","zoneid":"1","httpmethod":"GET","templateid":"202","domainid":"1","networkids":"204","id":"26","hostid":"4","account":"admin","ctxAccountId":"1","ctxStartEventId":"275"}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-12-19 16:22:08,074 INFO [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-28:ctx-6e488e85) Add job-82 into job monitoring
> 2013-12-19 16:22:08,075 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-28:ctx-6e488e85) Executing AsyncJobVO {id:82, userId: 1, accountId: 1, instanceType: VirtualMachine, instanceId: 26, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: {"serviceofferingid":"1","cmdEventType":"VM.CREATE","ctxUserId":"1","zoneid":"1","httpmethod":"GET","templateid":"202","domainid":"1","networkids":"204","id":"26","hostid":"4","account":"admin","ctxAccountId":"1","ctxStartEventId":"275"}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-12-19 16:22:08,077 DEBUG [c.c.a.ApiDispatcher] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) InfrastructureEntity name is:com.cloud.offering.ServiceOffering
> 2013-12-19 16:22:08,077 DEBUG [c.c.a.ApiDispatcher] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) ControlledEntity name is:com.cloud.template.VirtualMachineTemplate
> 2013-12-19 16:22:08,078 DEBUG [c.c.a.ApiDispatcher] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) ControlledEntity name is:com.cloud.network.Network
> 2013-12-19 16:22:08,105 DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Service SecurityGroup is not supported in the network id=204
> 2013-12-19 16:22:08,108 DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Service SecurityGroup is not supported in the network id=204
> 2013-12-19 16:22:08,108 DEBUG [c.c.v.UserVmManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Destination Host to deploy the VM is specified, specifying a deployment plan to deploy the VM
> 2013-12-19 16:22:08,121 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Deploy avoids pods: [], clusters: [], hosts: []
> 2013-12-19 16:22:08,122 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) DeploymentPlanner allocation algorithm: com.cloud.deploy.FirstFitPlanner@28cc6a8
> 2013-12-19 16:22:08,122 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:1, requested cpu: 500, requested ram: 536870912
> 2013-12-19 16:22:08,122 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Is ROOT volume READY (pool already allocated)?: No
> 2013-12-19 16:22:08,122 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) DeploymentPlan has host_id specified, choosing this host and making no checks on this host: 4
> 2013-12-19 16:22:08,124 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Looking for suitable pools for this host under zone: 1, pod: 1, cluster: 1
> 2013-12-19 16:22:08,125 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Checking suitable pools for volume (Id, Type): (29,ROOT)
> 2013-12-19 16:22:08,125 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) We need to allocate new storagepool for this volume
> 2013-12-19 16:22:08,126 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Calling StoragePoolAllocators to find suitable pools
> 2013-12-19 16:22:08,126 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2013-12-19 16:22:08,126 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) ClusterScopeStoragePoolAllocator looking for storage pool
> 2013-12-19 16:22:08,126 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Looking for pools in dc: 1 pod:1 cluster:1
> 2013-12-19 16:22:08,129 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Checking if storage pool is suitable, name: null ,poolId: 1
> 2013-12-19 16:22:08,131 DEBUG [c.c.s.StorageManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Checking pool 1 for storage, totalSize: 998772830208, usedBytes: 164892803072, usedPct: 0.1650954031635604, disable threshold: 0.85
> 2013-12-19 16:22:08,135 DEBUG [c.c.s.StorageManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Checking pool: 1 for volume allocation [Vol[29|vm=26|ROOT]], maxSize : 1997545660416, totalAllocatedSize : 76330872320, askingSize : 17179869184, allocated disable threshold: 0.85
> 2013-12-19 16:22:08,136 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) ClusterScopeStoragePoolAllocator returning 1 suitable storage pools
> 2013-12-19 16:22:08,136 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM
> 2013-12-19 16:22:08,136 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Checking if host: 4 can access any suitable storage pool for volume: ROOT
> 2013-12-19 16:22:08,137 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Host: 4 cannot access pool: 1
> 2013-12-19 16:22:08,137 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Could not find a potential host that has associated storage pools from the suitable host/pool lists for this VM
> 2013-12-19 16:22:08,137 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Cannnot deploy to specified host, returning.
> 2013-12-19 16:22:08,138 DEBUG [c.c.v.UserVmManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Destroying vm VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9] as it failed to create on Host with Id:4
> 2013-12-19 16:22:08,141 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) VM state transitted from :Stopped to Error with event: OperationFailedToErrorvm's original host id: null new host id: null host id before state transition: null
> 2013-12-19 16:22:08,169 WARN [o.a.c.alerts] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 26, on Host with Id: 4
> 2013-12-19 16:22:08,188 INFO [o.a.c.a.c.u.v.DeployVMCmd] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]Scope=interface com.cloud.dc.DataCenter; id=1
> 2013-12-19 16:22:08,189 INFO [o.a.c.a.c.u.v.DeployVMCmd] (Job-Executor-28:ctx-6e488e85 ctx-2b3b4192) Unable to create a deployment for VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]Scope=interface com.cloud.dc.DataCenter; id=1
> at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:210)
> at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3558)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3140)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3126)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy170.startVirtualMachine(Unknown Source)
> at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
> at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
> at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:521)
> at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> 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)
> 2013-12-19 16:22:08,190 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-28:ctx-6e488e85) Complete async job-82, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable to create a deployment for VM[User|VM-7c9d1adb-0945-4348-93d1-c3b86e8a2cc9]"}
> 2013-12-19 16:22:08,201 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-28:ctx-6e488e85) Done executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-82
> 2013-12-19 16:22:08,205 INFO [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-28:ctx-6e488e85) Remove job-82 from job monitoring
> 2013-12-19 16:22:09,651 DEBUG [c.c.s.StatsCollector] (StatsCollector-1:ctx-ec27359f) HostStatsCollector is running...
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)