That setting is currently set to 8 hours, but I agree, that is for the
conversion process.
I can connect to vCenter from the management server. Nothing is being blocked
there. In the management server logs I can see each VM, disk and networking
information being pulled one at a time. The failure message occurs at exactly
10 minutes, but the logs will continue to pull data from vCenter.
I opened Chrome's developer tools and found this error:
Error: timeout of 600000ms exceeded - plugins.js:213
at e.exports (createError.js:16:15)
at c.ontimeout (xhr.js:111:14)
The vCenter I'm connecting to has a little over 1k VMs/templates. The logs
indicate it takes its time with each VM, so hitting 600000ms makes sense. Just
need to find where that timeout is set and increase it.
-----Original Message-----
From: Nux <n...@li.nux.ro>
Sent: Friday, February 23, 2024 7:58 AM
To: users@cloudstack.apache.org
Cc: Kevin Seales <kevin.sea...@insiteone.com.invalid>
Subject: Re: VMware Import Timeout
[You don't often get email from n...@li.nux.ro. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
I think the setting you tried to change is
convert.vmware.instance.to.kvm.timeout, but that has to do with the conversion
process itself.
If you try with telnet or curl from the shell of the Cloudstack management
server, can you reach the VCenter?
On 2024-02-22 15:35, Kevin Seales wrote:
> We are trying to use the "Import-Export Instances" tool in ACS to test
> migration from VMware to ACS. After selecting "List VMware
> Instances", it hangs for 10 minutes, then ACS gives a very detailed
> error saying "Request Failed." The management logs show ACS is still
> receiving data from vCenter for another 2 or 3 minutes after the
> failure message. I'm assuming we are hitting a time out somewhere. I
> tried adjusting what I could find under global settings that may be related
> but the error
> still occurs. Does anyone know how we can resolve this issue?
