Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No online targets could be found for the required platform with a provisioning score above 0 #1274

Open
3 tasks done
xigasa opened this issue Dec 30, 2024 · 0 comments
Open
3 tasks done
Labels

Comments

@xigasa
Copy link

xigasa commented Dec 30, 2024

Operating System

Debian 11 bullseye, Ubuntu 22.04, Windows 10 64 bit

AMP Version and Build Date

2.6.0.6 - 20241120.1 / 2.6.0.8 - 20250122.3

AMP Release Stream

Mainline

I confirm that

  • I have searched for an existing bug report for this issue.
  • I am using the latest available version of AMP.
  • my operating system is up-to-date.

Intended Action

Deploy Template from controller to target

Expected Behaviour

The template to deploy on one of the available servers

Actual Behaviour

Controller is giving error "No online targets could be found for the required platform with a provisioning score above 0", its not logging any information even after putting logs into debug mode about the provisioning score even being attempted or calculated/ reaching out to targets for said score.

Reproduction

Create target in VPS (Tested in AWS and CloudServer, any version os) setup Wireguard vpn so vps(Target) can communicate locally / encrypted until it reaches the subnet with the target servers on it. Create target amp installation on subnet successfully pair target to controller. Tested full deployment/management of an Minecraft instance to verify functionality. Remove Said test instance. Follow [Configuring AMP for Enterprise or Advanced Usage] Guide to configure template role/perms/create template eg. 4gb Minecraft. Test template deployment and then you get said msg about provisioning score not above 0.

Here is the chat where Potato King had the same issue and iceofwraith2 started to help then went ghost. I also found digging threw 30 or 40 previous tickets I found someone else having the same/similar issue and Mike troubleshoot it and then stated he would look into it more and add a debug tag to the provisioning score in the next update so it would show the score in the logs however it didn't seem to make it into the last update as the ticket I had found was for a couple older version of amp I believe.
https://discord.com/channels/266012086423912458/1316594901806350358

This was also tested locally as in no vps and all on the same network and same result.

Just re-tested in amp 2.6.0.8 - 20250122.3

@xigasa xigasa added the bug label Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant