cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Likitha Shetty (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-8126) [VMware] Fix cold migration across clusters
Date Wed, 24 Dec 2014 09:53:13 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Likitha Shetty resolved CLOUDSTACK-8126.
----------------------------------------
    Resolution: Fixed

> [VMware] Fix cold migration across clusters
> -------------------------------------------
>
>                 Key: CLOUDSTACK-8126
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8126
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.5.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: Future
>
>
> +Steps to reproduce+
> 1. Have a setup with 2 clusters with a primary storage each (C1 and C2).
> 2. Deploy VM (Say it is in C1).
> 3. Stop the VM.
> 4. Migrate VM to a host in C2.
> 5. Start the VM.
> VM will fail to start in C2 and so will be migrated back to C1 and started up in a host
in C1.
> VM fails to start in the right cluster with the below error-
> {noformat}
> 2014-11-28 09:49:39,770 WARN  [c.c.h.v.r.VmwareResource] (DirectAgent-187:ctx-7ed1033d
10.147.40.28, job-399/job-401, cmd: StartCommand) StartCommand failed due to Exception: java.lang.RuntimeException
> Message: The name 'newvm' already exists.
> java.lang.RuntimeException: The name 'newvm' already exists.
>     at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:335)
>     at com.cloud.hypervisor.vmware.mo.HostMO.createVm(HostMO.java:559)
>     at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.createBlankVm(HypervisorHostHelper.java:1191)
>     at com.cloud.hypervisor.vmware.mo.HostMO.createBlankVm(HostMO.java:745)
>     at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1544)
>     at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:449)
>     at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:304)
>     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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>     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:722)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message