You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by cr...@istream.today on 2022/04/01 04:55:09 UTC
RE: Migration fail - Unable to find the target datastore
Hello,
Yes, everything else works, I have many VMs. This error is persistent in
all my 3 cloudstack setups.
This is the ID da097676-7fa7-4b9c-b962-a2fe467fe565 in cloudstack with
this cloud.uuid : da097676-7fa7-4b9c-b962-a2fe467fe565 in VMware.
Regards,
Cristian
-----Original Message-----
From: Abhishek Kumar <Ab...@shapeblue.com.INVALID>
Sent: Thursday, March 31, 2022 8:43 AM
To: users@cloudstack.apache.org
Subject: Re: Migration fail - Unable to find the target datastore
Hi Cristian,
Are you able to deploy a new VM on this particular storage pool - UUID:
da097676-7fa7-4b9c-b962-a2fe467fe565?
Also, in your vCenter can you please check if target host (to which VM is
being migrated) does have a datastore attached with name -
da0976767fa74b9cb962a2fe467fe565.
Essentially, here CloudStack VMware plugin is failing to find the
corresponding datastore for the storage pool that you selected for
migration.
Regards,
Abhishek
________________________________
From: cristian.c@istream.today <cr...@istream.today>
Sent: 30 March 2022 21:19
To: 'Nux' <nu...@li.nux.ro>; users@cloudstack.apache.org
<us...@cloudstack.apache.org>
Subject: RE: Migration fail - Unable to find the target datastore
Hi,
No, this is a different issue " Unable to find the target datastore".
Regards,
Cristian
---Original Message-----
From: Nux <nu...@li.nux.ro>
Sent: Wednesday, March 30, 2022 5:08 PM
To: users@cloudstack.apache.org
Cc: cristian.c@istream.today
Subject: Re: Migration fail - Unable to find the target datastore
Hi,
Isn't it this all over again?
https://github.com/apache/cloudstack/issues/4187
---
Nux!
www.nux.ro
On 2022-03-29 20:08, cristian.c@istream.today wrote:
> I forgot to mention that I was trying first to migrate the volume and
> start the VM, but I get error on trying to migrate the volume ( Vmware
> local storge ) Unable to access the virtual machine configuration:
> Unable to access file [ro002] i-2-351-VM/i-2-351-VM.vmx, then I was
> trying with "Migrate instance to another primary storage" which gives
> the bellow error..
>
>
>
> From: cristian.c@istream.today <cr...@istream.today>
> Sent: Tuesday, March 29, 2022 9:21 PM
> To: users@cloudstack.apache.org
> Subject: Migration fail - Unable to find the target datastore
>
>
>
> Hello,
>
>
>
> Any idea why the migration fail with this error? I have the same
> error starting with CloudStack 4.16 ( also had some erros with 4.15,
> worked before with older ACS ) I just did an update today to 4.16.1
> and I see the same error..
>
>
>
>
>
> Error :
>
> 022-03-29 18:11:04,052 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-13:null) (logid:) SeqA 3-1551701: Sending Seq
> 3-1551701: { Ans: , MgmtId: 39908814623087, via: 3, Ver: v1, Flags:
> 100010,
>
[{"com.cloud.agent.api.AgentControlAnswer":{"result":"true","wait":"0","bypa
> ssHostMaintenance":"false"}}] }
>
> 2022-03-29 18:11:04,067 ERROR [c.c.h.v.r.VmwareResource]
> (DirectAgent-256:ctx-43438d6c spb-ro-002.domain.host,
> job-2647/job-2648,
> cmd: MigrateVmToPoolCommand) (logid:e122e3d6) Unable to find the
> target
> datastore: da097676-7fa7-4b9c-b962-a2fe467fe565 in datacenter: RO-01
> to execute migration
>
> 2022-03-29 18:11:04,118 ERROR [c.c.h.v.r.VmwareResource]
> (DirectAgent-256:ctx-43438d6c spb-ro-002.domain.host,
> job-2647/job-2648,
> cmd: MigrateVmToPoolCommand) (logid:e122e3d6) Change data store for VM
> i-2-351-VM failed: Unable to find the target datastore:
> da097676-7fa7-4b9c-b962-a2fe467fe565 in datacenter: EU-ro-01 to
> execute migration
>
> 2022-03-29 18:11:04,120 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-256:ctx-43438d6c) (logid:e122e3d6) Seq
> 25-1196268651020288049:
> Response Received:
>
> 2022-03-29 18:11:04,121 DEBUG [c.c.a.t.Request]
> (DirectAgent-256:ctx-43438d6c) (logid:e122e3d6) Seq
> 25-1196268651020288049:
> Processing: { Ans: , MgmtId: 39908814623087, via:
> 25(spb-ro-002.domain.host), Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":"false","details":"Exception:
> com.cloud.utils.exception.CloudRuntimeException
>
> Message: Change data store for VM i-2-351-VM failed
>
> Stack: com.cloud.utils.exception.CloudRuntimeException: Change data
> store for VM i-2-351-VM failed
>
> at
>
com.cloud.hypervisor.vmware.resource.VmwareResource.migrateAndAnswer(VmwareR
> esource.java:4550)
>
> at
>
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.j
> ava:4507)
>
> at
>
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareRes
> ource.java:501)
>
> at
>
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAtta
> che.java:315)
>
> at
>
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedCo
> ntextRunnable.java:48)
>
> at
>
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Defa
> ultManagedContext.java:55)
>
> at
>
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCon
> text(DefaultManagedContext.java:102)
>
> at
>
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCont
> ext(DefaultManagedContext.java:52)
>
> at
>
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCont
> extRunnable.java:45)
>
> at
>
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java
> :515)
>
> at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>
> at
>
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTa
> sk.run(ScheduledThreadPoolExecutor.java:304)
>
> at
>
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecut
> or.java:1128)
>
> at
>
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecu
> tor.java:628)
>
> at java.base/java.lang.Thread.run(Thread.java:829)
>
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
> find the target datastore: da097676-7fa7-4b9c-b962-a2fe467fe565 in
> datacenter:
> EU-ro-01 to execute migration
>
> at
>
com.cloud.hypervisor.vmware.resource.VmwareResource.relocateVirtualMachine(V
> mwareResource.java:7588)
>
> at
>
com.cloud.hypervisor.vmware.resource.VmwareResource.migrateAndAnswer(VmwareR
> esource.java:4545)
>
> ... 14 more
>
>
>
>
>
> I have tested with different hosts, zones, all with 4.16.x and VMware
> 6.5
> u3. Any suggestions?
>
>
>
>
>
>
>
> Thank you,
>
> Cristian