[SOLVED] WAPT Agent 2.6 → 2.7 update issue on Ubuntu 26.04

[happy-day]

Good morning,

I am having trouble updating tis-waptagent and tis-waptagent-gui from version 2.6 to 2.7 on Ubuntu 26.04 LTS (resolute) automatically via your repository.
WAPT Discovery server version
WAPT Server version: 2.7.0.19598
WAPT Agent version: 2.7.0.19598
WAPT Setup version: 2.7.0.19598
WAPT Deploy version: 2.7.0.19598

My WAPT 2.7 APT repository is configured as follows:

Code: Select all

/etc/apt/sources.list.d/tis-waptagent.sources
Architectures: amd64
Components: main
X-Repolib-Name: tis-waptagent
Signed-By: /etc/apt/keyrings/tis-waptagent.gpg
Suites: resolute
Types: deb
URIs:  https://wapt.tranquil.it/Ubuntu/wapt-2.7/

The repository is accessible and the APT resolute/amd64 index is responding correctly:

Code: Select all

curl -I https://wapt.tranquil.it/Ubuntu/wapt-2.7/dists/resolute/main/binary-amd64/Packages

However, when I look at the index contents, I only get tis-waptserver tis-waptsetup:

Code: Select all

curl -s https://wapt.tranquil.it/Ubuntu/wapt-2.7/dists/resolute/main/binary-amd64/Packages | grep -E '^(Package|Version|Filename):'
Package: tis-waptserver
Version: 2.7.0.19598-b35845cd-amd64
Filename: pool/main/t/tis-waptserver/tis-waptserver_2.7.0.19598-b35845cd-amd64_amd64.deb

Package: tis-waptsetup
Version: 2.7.0.19598-b35845cd-amd64
Filename: pool/main/t/tis-waptsetup/tis-waptsetup_2.7.0.19598-b35845cd-amd64_all.deb

Therefore, there are no entries for:

tis-waptagent
tis-waptagent-gui

However, the tis-waptagent 2.7 package does exist in the WAPT 2.7 releases.
However, it can be found here: https://wapt.tranquil.it/wapt/releases/wapt-2.7/

On the machine:

Code: Select all

apt-cache policy tis-waptagent
 tis-waptagent:
  Installé : 2.6.1.17870-d3b9238d-amd64
  Candidat : 2.6.1.17870-d3b9238d-amd64

APT therefore does not see any version 2.7 available.

Same problem for tis-waptagent-gui.

I successfully updated it manually:

Code: Select all

wget https://wapt.tranquil.it/wapt/releases/wapt-2.7.0.19598-b35845cd/tis-waptagent-2.7.0.19598-b35845cd-amd64.deb
wget https://wapt.tranquil.it/wapt/releases/wapt-2.7.0.19598-b35845cd/tis-waptagent-gui-2.7.0.19598-b35845cd-amd64.deb

sudo dpkg -i tis-waptagent-gui-2.7.0.19598-b35845cd-amd64.deb
sudo dpkg -i tis-waptagent-2.7.0.19598-b35845cd-amd64.deb

I would therefore like to continue updating automatically via the repository
Thank you for your clarifications.

[dcardon]

Hello "happy-day",

Enterprise/Discovery version? See forum rules.

Pointing the agent directly to our WAPT repositories is no longer considered best practice. It's preferable for the agent to be in the same release as the server. However, if the agent points directly to Tranquil IT's WAPT repositories, it risks being a more recent version.

Therefore, it's preferable to import the .deb package onto your server and use it for the initial installation, and then perform updates using a WAPT package. This is why the agent .deb packages were not synchronized to the Debian/Ubuntu 2.7 repository.

That said, these agents are available in the directory https://wapt.tranquil.it/wapt/releases/.

Since the documentation hasn't been updated yet, I'll check with my colleagues to have them push the corresponding .deb packages to the .deb repository, and we'll remove them once the documentation is up to date.

Best regards,

Denis

[happy-day]

Hello Denis,
Thank you for your reply (I've edited my first message with the server version information).
I'm not sure I understand your answer; we don't use the WAPT agent on our GNU/Linux machines.
We use it exclusively for our Windows machines.
As indicated in your documentation
, "The WAPT Console must be installed on the administration workstation from which you manage your network."
The console and the tranquil.it repository are exclusively on our administration machines, which are running Ubuntu.
Indeed, the documentation isn't entirely up-to-date (see the attached image):
https://www.wapt.fr/fr/doc-2.7/wapt-configuration.html

Have a good afternoon.

[dcardon]

Hello "happy-day",

indeed there is a GUI to download the agents and create the update packages in the console, but it might only be available in the enterprise version.

For now, you can retrieve the .deb files from the provided URL. For the admin workstations, they have the agent installed but not attached to the WAPT server?

The best approach is to build the agent upgrade packages from the console and assign them to the workstations (removing the source apt configuration from the agents).

Regards,

Denis