opsi-client-agent 4.2.0.37-2 (released to stable on 12.08.) has two problems regarding special configurations:
1. if a configstate "opsiclientd.depot_server.url" is set (we recommend using clientconfig.depot.id and clientconfig.depot.protocol instead)
2. if two startup events are used simultanously (gui_startup and opsiclientd_start)
Both problems are fixed in opsi-client-agent 4.2.0.39-1 which is now released to stable and testing.
We recommend not to roll out opsi-client-agent 4.2.0.37-2 or 4.2.0.38-1 and instead use 4.2.0.39-1.
I appologize for the inconveniance.
Best Regards,
Nils Dörrer
Changelogs:
Code: Alles auswählen
opsi-client-agent (4.2.0.39-1) stable; urgency=low
* Updated opsiclientd to 4.2.0.128 (fixed colliding startup event handling, fixed handling of opsiclientd.depot_server.url)
-- Nils Doerrer <n.doerrer@uib.de> Mon, 15 Aug 2022 12:00:00 +0100
opsi-client-agent (4.2.0.38-1) stable; urgency=low
* Updated oca-installation-helper to 4.2.0.22
* Updated opsiclientd to 4.2.0.126 (dualstack connection to controlserver, fixed warnings)
-- Nils Doerrer <n.doerrer@uib.de> Tue, 02 Aug 2022 17:00:00 +0100