Timeout while waiting for async task

[tagnullde]

While following the install guides from the Ludus website and goad itself, I encountered this error:

VMs have been created by the "install" command:

"Check" seems good too:

When running "install", I can see the CPU workload going up and fluctuating between 10% and 70%. with rare spikes to 90% for a second or two. RAM is only 50-60% used. Since the VMs are already present, I don't think the Diskspace is the culprit.

I set the $WIN_ASYNC_STARTUP_TIMEOUT to 3000 too. Doesn't seem to do much, if anything.

Any ideas?

[finack42]

I'm facing exactly the same issue with the same setup (Ludus/Proxmox).

[Clipsec]

Same here. We have some info on fixing?

[kusk]

Same error here:

[kusk]

To those having the same problem. Check your /root/.goad/goad.ini. My pm_api_url was pointing to a wrong IP.

[tagnullde]

This seems to be the solution. I had also the wrong IP there.
Right now it seems to be installing just fine. It's not done yet. But I already see the LUDUS Wallpaper on some machines.

Thanks @kusk for letting us know.

[finack42]

To those having the same problem. Check your /root/.goad/goad.ini. My pm_api_url was pointing to a wrong IP.

Isn't the [proxmox] section ignored when selecting Ludus as a provider? For example, the next variable pm_user isn't used neither in case of Ludus.

I think this is still a timing issue. I managed to set it up successfully by creating an empty lab and then did provide a 2-3 times until all the VMs has the right IP addresses. Then I disabled the firewall and forced WinRM to use HTTP (Port 5985). After that I started the Ansible scripts with provision_lab and everything finished without any errors.

[tagnullde]

To those having the same problem. Check your /root/.goad/goad.ini. My pm_api_url was pointing to a wrong IP.

Isn't the [proxmox] section ignored when selecting Ludus as a provider? For example, the next variable pm_user isn't used neither in case of Ludus.

I don't know, I have never worked with Ludus, Proxmox or ansible before. But what I can say is that after changing the IP to the actual location of the API, it worked right away. Maybe you had a different problem but the same error message?

[Obscurity1008]

The incorrect IPs are being populated in the Ansible inventory. The inventory file adheres to the IP range, but when the IPs are set on the hosts, they do not.

For example, an IP range of 10.10.10 results in an inventory being set to 10.10.10.22 for DC-1, but the actual IP was 10.5.10.50.

For now, I just updated the IP in the workspace inventory and ran provision_lab, unless I am doing something wrong, this is a bug.