Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BAE8110FC1 for ; Thu, 1 Aug 2013 06:01:51 +0000 (UTC) Received: (qmail 30719 invoked by uid 500); 1 Aug 2013 06:01:51 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 30691 invoked by uid 500); 1 Aug 2013 06:01:51 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 30596 invoked by uid 500); 1 Aug 2013 06:01:51 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 30542 invoked by uid 99); 1 Aug 2013 06:01:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Aug 2013 06:01:51 +0000 Date: Thu, 1 Aug 2013 06:01:51 +0000 (UTC) From: "Ram Ganesh (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-3895) VM Migration across VMWARE clusters which are added with different switches(StandardSwith,DVS,Nexus) should error out saying "Migration is not supproted across different switches" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-3895?page=3Dcom.atl= assian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-3895: ----------------------------------- Assignee: Sateesh Chodapuneedi =20 > VM Migration across VMWARE clusters which are added with different switch= es(StandardSwith,DVS,Nexus) should error out saying "Migration is not suppr= oted across different switches" > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------------- > > Key: CLOUDSTACK-3895 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-389= 5 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the defa= ult.)=20 > Components: Network Controller, VMware > Affects Versions: 4.2.0 > Reporter: Sailaja Mada > Assignee: Sateesh Chodapuneedi > Fix For: 4.2.0 > > Attachments: apilog.log, management-server.log > > > Steps: > 1. Tried to migrate VM from VMWARE DVS to Stand Vswitch cluster. > It failed as host added with standard switch does not have VDS .=20 > DVS has cluster scope. Hence migration of VM is supported across cluster = with DVS as the backend vswitch. But if another cluster has vswitch as bac= kend then we don=E2=80=99t support migration between those clusters with di= fferent backend vswitches > VM Migration across VMWARE clusters which are added with different switch= es(StandardSwith,DVS,Nexus) should error out saying "Migration is not suppr= oted across different switches" . > Details of the error log : > -------------------------------------------------------------------------= --------------------------------------------------- > 2013-07-05 16:08:11,648 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-E= xecutor-100:job-243) release mem from host: 6, old used: 536870912,reserved= : 0, total: 34346127360; new used: 0,reserved:0; movedfromreserved: false,m= oveToReserveredfalse > 2013-07-05 16:08:11,685 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Exec= utor-100:job-243) Unexpected exception while executing org.apache.cloudstac= k.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm VM= [User|instance2] along with its volumes. com.cloud.utils.exception.CloudRun= timeException: Error while migrating the vm VM[User|instance2] to host Host= [-6-Routing]. Exception: java.lang.RuntimeException > Message: Network card 'Network adapter 1' has a DVPort backing, which is = not supported. This could be because the host does not support VDS or becau= se the host has not joined a VDS. > Stack: java.lang.RuntimeException: Network card 'Network adapter 1' has a= DVPort backing, which is not supported. This could be because the host doe= s not support VDS or because the host has not joined a VDS. > at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(Vmwa= reClient.java:290) > at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.migrate(Virtua= lMachineMO.java:329) > at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(Vm= wareResource.java:3638) > at com.cloud.hypervisor.vmware.resource.VmwareResource.executeReq= uest(VmwareResource.java:420) > at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgen= tAttache.java:186) > 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.ScheduledThreadPoolExecutor$ScheduledFutu= reTask.access$101(ScheduledThreadPoolExecutor.java:165) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutu= reTask.run(ScheduledThreadPoolExecutor.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolEx= ecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE= xecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > at com.cloud.storage.VolumeManagerImpl.migrateVolumes(VolumeManag= erImpl.java:2177) > at com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(Virt= ualMachineManagerImpl.java:1682) > at com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume= (UserVmManagerImpl.java:4035) > at com.cloud.utils.component.ComponentInstantiationPostProcessor$= InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:12= 5) > at org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachi= neWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:137) > 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(ThreadPoolEx= ecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE= xecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-05 16:08:11,686 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Exec= utor-100:job-243) Complete async job-243, jobStatus: 2, resultCode: 530, re= sult: Error Code: 530 Error text: Failed to migrated vm VM[User|instance2] = along with its volumes. com.cloud.utils.exception.CloudRuntimeException: Er= ror while migrating the vm VM[User|instance2] to host Host[-6-Routing]. Exc= eption: java.lang.RuntimeException > Message: Network card 'Network adapter 1' has a DVPort backing, which is = not supported. This could be because the host does not support VDS or becau= se the host has not joined a VDS. > Stack: java.lang.RuntimeException: Network card 'Network adapter 1' has a= DVPort backing, which is not supported. This could be because the host doe= s not support VDS or because the host has not joined a VDS. > at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(Vmwa= reClient.java:290) > at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.migrate(Virtua= lMachineMO.java:329) > at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(Vm= wareResource.java:3638) > at com.cloud.hypervisor.vmware.resource.VmwareResource.executeReq= uest(VmwareResource.java:420) > at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgen= tAttache.java:186) > 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.ScheduledThreadPoolExecutor$ScheduledFutu= reTask.access$101(ScheduledThreadPoolExecutor.java:165) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutu= reTask.run(ScheduledThreadPoolExecutor.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolEx= ecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE= xecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-05 16:08:13,001 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:nul= l) =3D=3D=3DSTART=3D=3D=3D 10.144.6.19 -- GET command=3DqueryAsyncJobResu= lt&jobId=3Da01d3615-fbe2-4f7e-9131-c3f59337dfae&response=3Djson&sessionkey= =3Dqw5mLlCQwn4ujTscAsUpfLYk2xQ%3D&_=3D1373020877862 > 2013-07-05 16:08:13,014 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina= -exec-3:null) Async job-243 completed > 2013-07-05 16:08:13,020 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:nul= l) =3D=3D=3DEND=3D=3D=3D 10.144.6.19 -- GET command=3DqueryAsyncJobResult= &jobId=3Da01d3615-fbe2-4f7e-9131-c3f59337dfae&response=3Djson&sessionkey=3D= qw5mLlCQwn4ujTscAsUpfLYk2xQ%3D&_=3D1373020877862 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira