Application Deployment - Cannot create the instance

System Information

Field Value
Operating System Linux - Debian GNU/Linux 11 on x86_64
Product AMP ‘Phobos’ v2.6.0.6 (Mainline)
Virtualization QEMU_KVM
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Task

Create instance after rollback

Problem Description

Issue

We had troubles with our instance, and after a rollback and an license key trouble (seen with Hostinger support), we cannot create instances.
This task could not be completed: Create instance - Minecraft - State: 3.

Reproduction Steps

  • Rollback the instance to an old state
  • Struggle with license key activation, Hostinger support solve the issue
  • Cannot create an instance, get the error "This task could not be completed: Create instance - Minecraft - State: 3.

Read the deployment log to see what could be going wrong

This is what I have in the logs when I try to create an instance :

[09:53:08] [InstanceManager:Omega_Bot Warning/20] : Non-managed instances exist, autoconfigure cannot guarantee that the configuration is valid!
[09:53:08] [System:Omega_Bot Warning/20] : Create Instance Failed: The core archive failed to download or unpack: Failed to find a release matching the specified version: LTS/ - This version may no longer be available to download, you should update to a newer version.

This happens even after verifying that everything is up to date.
We are currently running version 2.6.0.6 - 20241120.1

What’s the output of ampinstmgr version in the Linux CLI?

ampinstmgr version

[Info/1] AMP Instance Manager v2.5.1.8 built 17/09/2024 12:32
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV

We have a different version shown here.

You need to update your CLI tools

Hello, sorry for the delay,

We updated to v 2.6, and we still encounter the same issue. One thing to note is that an empty folder is created when we create a game instance, that we cannot delete (Could not find a part of the path ‘/home/amp/.ampdata/instances/folderName’)

Run ampinstmgr fixperms as root to resolve any possible file perm issues, beyond that I’d suggest reading the ADS’s Deployment Log to see what’s going on