Page 1 of 1

[RESOLVED] Version 2.3: First bug: no packages visible in a target's configuration

Published: January 10, 2023 - 3:06 PM
by t.heroult
Hello,

I updated the WAPT server to version 2.3.
When I go to the configuration of a machine (with the new agent or the old one, it's the same), the list of available packages only contains packages created after the server update!

In the repository, all the packages are still present, but it is now impossible to add one to a target.

Re: Version 2.3: First bug: no packages visible in a target's configuration

Published: January 10, 2023 - 3:55 PM
by Littlebox
Hello,

I had the same issue; by re-signing the packages, it was possible to assign them to the hosts again.

Re: Version 2.3: First bug: no packages visible in a target's configuration

Published: January 10, 2023 - 3:59 PM
by htouvet
During the database upgrade, the table of available packages is recreated (because in some installations, package UUIDs were duplicated)

but it is not re-populated with the contents of the packages.

You can do this with the command:

(debian)

Code: Select all

wapt-scanpackages -b /var/www/wapt

Re: Version 2.3: First bug: no packages visible in a target's configuration

Published: January 10, 2023 - 4:26 PM
by t.heroult
The command works fine, everything is OK :)

. Thank you!