Restore fails when application module is not in any repository

[gsanchietti]

Introduction:
When attempting to restore an application backup on a freshly installed, stable version of NS8, the restore procedure fails if the application's module is not present in any configured repository. The failure occurs during the eligibility check phase, preventing completion of the restore operation.

Steps to reproduce:

1. On a clean NS8 installation, configure at least one backup destination.
2. Install an application (e.g., Nextcloud) from the Software Center.
3. Perform a backup of the installed application.
4. Remove the application instance.
5. Disable the default repository from the Software Center.
6. Attempt to restore the backup of the application instance.

Expected behavior:
The system should be able to restore the application instance from backup, regardless of the repository state, or at least provide a clear message and guidance if the repository/module is missing.

Actual behavior:
The restore process fails during the "determine restore eligibility" step, with a "validation-failed" status. The failure is triggered because the application module is not present in any configured repository, blocking the restore operation.

UI error:

Determine restore eligibility
Task cluster/determine-restore-eligibility failed validation

restic dump 0654a404185815a56152861911601c07a8ab1ef63bbdf75fe478032616f761e7 state/environment

From log:

Jun 17 14:37:34 rl1.leader.cluster0.gs.nethserver.net agent@cluster[64014]: task/cluster/05a18742-dd64-4946-84f6-3ab52a08de4c: action "determine-restore-eligibility" status is "validation-failed" (2) at step 50determine_restore_eligibility

Components:

• NS8 (stable) 3.9.3
• Relevant module: e.g., Nextcloud (also tested with Dependency Track, see related issue)
• Backup/Restore subsystem

[DavidePrincipi]

@andre8244 this is a video of the error

Screencast.From.2025-08-01.16-45-43.webm

Discussion https://mattermost.nethesis.it/nethesis/pl/ouk9dhwhx7reiyspojxd9ofzec

[DavidePrincipi]

In Testing 3.9.3-dev.2

Test case 1

• Check the bug is not reproducible

Test case 2

• Use Mail for the test. In a multi-node cluster disable the Default repo and try to restore Mail in a different node. The node with the existing instance must be shown in a disabled state because of the max-per-node limit is reached.

[mrmarkuz]

Test case 1 verified

Test case 2 verified