[
https://issues.apache.org/jira/browse/CLOUDSTACK-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744692#comment-13744692
]
Sateesh Chodapuneedi commented on CLOUDSTACK-4375:
--------------------------------------------------
if currentPool is accessible to destination host, skip calling allocators and
move on to next volume to process.
This means if user calls migrateVirtualMachineWithVolume API where all volumes
of VM are accessible on specified target host, then API fails as there is no
storage migration involved. Instead user should call migrateVirtualMachine API.
We now warn user of each volume that doesn't require migration (accessible on
target host).
----
2013-08-20 04:16:20,517 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-2:job-40 = [ 793485ca-0a2f-4553-88f6-7e385d7c5f01 ]) Executing
org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd
for job-40 = [ 793485ca-0a2f-4553-88f6-7e385d7c5f01 ]
2013-08-20 04:16:20,618 WARN [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-2:job-40 = [ 793485ca-0a2f-4553-88f6-7e385d7c5f01 ]) Volume
ROOT-5 will not be migrated as it's current storage pool is accessible on host
10.102.192.11
2013-08-20 04:16:20,625 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-2:job-40 = [ 793485ca-0a2f-4553-88f6-7e385d7c5f01 ]) Unexpected
exception while executing
org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd
com.cloud.exception.InvalidParameterValueException: Migration of the vm
VM[User|m1]from host Host[-4-Routing] to destination host Host[-7-Routing]
doesn't involve migrating the volumes.
------
> VM Migration is failing from one cluster to another cluster.
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-4375
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4375
> 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: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> Steps followed are as below:
> 1)Created a Advanced Zone VMware setup with two clusters C1 & c2.
> 2)C1 having 2 hosts H1 and H2 and C2 having single host H3.
> 3)Dedicated the Zone to Domain D1 having Account A1 and A2.
> 4)Dedicated the Host H2 to Account A1, where H1 has the system Vm's in it.
> 5)Created a VM not using the affinity group for the host,the Router VM came
> up on the host H1and the VM is created on host H3 of the cluster C2.
> 6)Now tried to migrate the VM from H3 to H1 the migration was successful.
> 7)Now tried to migrate the VM from H1 to H3 again the VM migration failed
> with the below error message
> "2013-08-17 03:13:59,447 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
> ===START=== 10.101.255.76 -- GET
> command=migrateVirtualMachine&hostid=49537136-d44f-439a-937c-442ed74bd697&virtualmachineid=385b5edb-b6b2-4931-a4ab-8f9bd96acd14&response=json&sessionkey=3O%2FKhJ6pMFCAfLTZtIqQOY6R6%2F4%3D&_=1376669973550
> 2013-08-17 03:13:59,488 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-2:null) submit async job-178 = [
> b9d65e31-7cdf-4ce5-b93c-440287d8523f ], details: AsyncJobVO {id:178, userId:
> 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null,
> cmdInfo:
> {"response":"json","sessionkey":"3O/KhJ6pMFCAfLTZtIqQOY6R6/4\u003d","virtualmachineid":"385b5edb-b6b2-4931-a4ab-8f9bd96acd14","cmdEventType":"VM.MIGRATE","hostid":"49537136-d44f-439a-937c-442ed74bd697","ctxUserId":"2","httpmethod":"GET","_":"1376669973550","ctxAccountId":"2","ctxStartEventId":"618"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-08-17 03:13:59,489 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
> ===END=== 10.101.255.76 -- GET
> command=migrateVirtualMachine&hostid=49537136-d44f-439a-937c-442ed74bd697&virtualmachineid=385b5edb-b6b2-4931-a4ab-8f9bd96acd14&response=json&sessionkey=3O%2FKhJ6pMFCAfLTZtIqQOY6R6%2F4%3D&_=1376669973550
> 2013-08-17 03:13:59,491 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Executing org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-178
> = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]
> 2013-08-17 03:13:59,528 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Migrating VM[User|kiran14] to
> Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
> : Dest[Zone(3)-Pod(3)-Cluster(6)-Host(11)-Storage()]
> 2013-08-17 03:13:59,529 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]) Source
> and destination host are not in same cluster, unable to migrate to host: 11
> 2013-08-17 03:13:59,536 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Source and destination host
> are not in same cluster, unable to migrate to host: 11
> at
> com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1452)
> at
> com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3981)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:147)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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)"
> Expected result:The VM migration should be successful.
> Note:The Vmotion on the VMware hosts is enabled.
--
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
