[
https://issues.apache.org/jira/browse/CLOUDSTACK-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743557#comment-13743557
]
ASF subversion and git services commented on CLOUDSTACK-4385:
-------------------------------------------------------------
Commit dd5ea8f2aa86221c67e66cc83b8c1e2f003f4066 in branch refs/heads/4.2 from
[~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dd5ea8f ]
CLOUDSTACK-4385 : [ZWPS]Across the cluster live migration of VM on zone wide
primary storage pool fails
If all the VM's volumes are on zone wide primary storage pool then live
migration of the VM would not involve storage migration. Hence MigrateVM API
would be called against MigrateVMWithVolume. So far PrepareForMigrationCommand
handled scenarios of VM moving across hosts within a cluster, but with zone
wide primary storage in picture this command need to handle scenarios of VM
moving across clusters. Try to find the VM in datacenter if not found within
cluster.
Signed-off-by: Sateesh Chodapuneedi <[email protected]>
> [ZWPS]Across the cluster live migration of VM on zone wide primary storage
> pool fails
> -------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4385
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4385
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.0
>
>
> If all the VM's volumes are on zone wide primary storage pool then live
> migration of the VM would not involve storage migration. Hence MigrateVM API
> would be called against MigrateVMWithVolume. So far
> PrepareForMigrationCommand handled scenarios of VM moving across hosts within
> a cluster, but with zone wide primary storage in picture this command need to
> handle scenarios of VM moving across clusters.
> Seeing following error when attempted to live migrate VM across clusters.
> 2013-08-19 01:39:06,629 INFO [vmware.resource.VmwareResource]
> (DirectAgent-195:10.102.192.3) Executing resource PrepareForMigrationCommand:
> {"vm":{"id":10,"name":"i-2-10-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"hostName":"m4","arch":"x86_64","os":"CentOS
> 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"de2f847499821763","params":{"rootDiskController":"ide","nicAdapter":"E1000","nestedVirtualizationFlag":"false"},"uuid":"f31dd0e7-6491-48f7-b7c1-ef5611bc0482","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"dcef2db7-57da-4ab2-a25b-4ad8f951da06","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"7b2ba866-ca87-3954-a935-a354f3889574","id":1,"poolType":"NetworkFilesystem","host":"10.102.192.100","path":"/cpg_vol/sree/p2","port":2049}},"name":"ROOT-10","size":2147483648,"path":"ROOT-10","volumeId":21,"vmName":"i-2-10-VM","accountId":2,"format":"OVA","id":21,"hypervisorType":"VMware"}},"diskSeq":0,"type":"ROOT"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"96f72019-d36d-4f3c-9235-0de86d8488a2","ip":"10.1.1.215","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:0d:ea:00:05","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://571","isolationUri":"vlan://571","isSecurityGroupEnabled":false,"name":"dvSwitch1"}]},"wait":0}
> 2013-08-19 01:39:06,633 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-195:10.102.192.3) Preparing host for migrating
> com.cloud.agent.api.to.VirtualMachineTO@13c0d87
> 2013-08-19 01:39:06,696 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-195:10.102.192.3) VM i-2-10-VM does not exist in VMware
> datacenter
> 2013-08-19 01:39:06,697 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-195:10.102.192.3) Unexcpeted exception Exception:
> java.lang.Exception
> Message: VM i-2-10-VM does not exist in VMware datacenter
> java.lang.Exception: VM i-2-10-VM does not exist in VMware datacenter
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3751)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:458)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.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$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> 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)
> 2013-08-19 01:39:06,698 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-195:null) Seq 3-449388837: Response Received:
> 2013-08-19 01:39:06,698 DEBUG [agent.transport.Request]
> (DirectAgent-195:null) Seq 3-449388837: Processing: { Ans: , MgmtId:
> 227080256212965, via: 3, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.PrepareForMigrationAnswer":{"result":false,"details":"Unexcpeted
> exception Exception: java.lang.Exception\nMessage: VM i-2-10-VM does not
> exist in VMware datacenter\n","wait":0}}] }
--
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
