Comment 14 for bug 1208393

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Hi, I can't get this feature to work.

I deployed lds trunk, created the upgrade profile with the autoremove flag enabled, registered a client that had one upgrade available and dozens of autoremove packages, watched exchanges:

(...)
2017-11-10 11:45:45,277 INFO [MainThread] Queuing message with changes in known packages: 118 installed, 9998 available, 0 available upgrades, 0 locked, 13 autoremovable, 0 not installed, 0 not available, 0 not available upgrades, 0 not locked, 0 not autoremovable.
2017-11-10 11:46:52,761 INFO [MainThread] Queuing message with changes in known packages: 100 installed, 8903 available, 0 available upgrades, 0 locked, 13 autoremovable, 0 not installed, 0 not available, 0 not available upgrades, 0 not locked, 0 not autoremovable.
(...)

But on the server the landscape-resource-1.computer_packages.autoremovable table row remained empty:
landscape-resource-1=# select available_upgrades,autoremovable from computer_packages;
 available_upgrades | autoremovable
--------------------+---------------
 {316069} | {}
(1 row)

When the upgrade time came, only the one package was upgraded, and the autoremovable ones remained installed.