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] [Updated] (CLOUDSTACK-7102) Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' expection
Date Thu, 17 Jul 2014 07:46:05 GMT

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

Likitha Shetty updated CLOUDSTACK-7102:
---------------------------------------

    Labels: S1  (was: )

> Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' expection
> ---------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7102
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7102
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller, VMware
>    Affects Versions: 4.2.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>            Priority: Critical
>              Labels: S1
>             Fix For: 4.5.0
>
>
> Steps to reproduce
> ------------------------
> 1. Set global config 'vm.instancename.flag' to true.
> 2. Bring up CS in advanced zone with at-least one vmware cluster.
> 3. Add two primary storages to the cluster.
> 4. Deploy one guest VM.
> 5. Create a volume and attach the volume to the guest VM. (Ensure the volume is in primary
storage that doesn't contain the root disk).
> 6. Migrate the volume to the primary storage that contains the root disk.
> Volume Migration will fail with the below error -
> {noformat}
> 2014-07-14 12:21:33,112 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-398:ctx-4797dd6a
10.102.192.7, job-878/job-879, cmd: MigrateVolumeCommand) Catch Exception java.lang.Exception
due to java.lang.Exception: VM i-2-32-VM does not exist in VMware datacenter datacenter-30215
> java.lang.Exception: VM i-2-32-VM does not exist in VMware datacenter datacenter-30215
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3139)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:416)
>         at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293)
>         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.run(FutureTask.java:262)
>         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:1145)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:744)
> {noformat}
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message