Bug 58934 - after 5.0 -> 5.2 upgrade, the new log-driver is only used after manual restart of the docker daemon
Summary: after 5.0 -> 5.2 upgrade, the new log-driver is only used after manual restar...
Status: RESOLVED MOVED
Alias: None
Product: UCS
Classification: Unclassified
Component: Docker
Version: UCS 5.2
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: Johannes Königer
QA Contact: Juan Pedro Torres
URL:
Keywords:
Depends on: 56058
Blocks:
  Show dependency treegraph
 
Reported: 2026-01-07 15:40 CET by Jürn Brodersen
Modified: 2026-01-27 19:14 CET (History)
11 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 7: Crash: Bug causes crash or data loss
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.360
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2025080621000219
Bug group (optional): Regression, Workaround is available
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jürn Brodersen univentionstaff 2026-01-07 15:40:48 CET
+++ This bug was initially created as a clone of Bug #56058 +++

After an update, we are not restarting docker after setting the log-driver variable https://git.knut.univention.de/univention/dev/ucs/-/blob/5.2-4/container/univention-docker/debian/univention-docker.postinst?ref_type=heads#L22

This means that any container created until the docker daemon is restarted is still using the old log-driver. This can not be changed after the image has been created. It needs to be recreated!

Context:
Kelvin >= 3 needs the journald driver to be able to redirect the logs to the http.log. While it is still possible to see the logs through docker logs, the old json-file log-driver has a shorter time until old logs will be deleted.

While we strongly recommend restarting the server after the update, I think this is still a problem for app upgrades.
Comment 1 Fabian Schneider univentionstaff 2026-01-08 08:02:34 CET
The cause of the issue is, that clients are not receiving the log entries in the http.log anymore - also not after restarting docker, the whole server or similar. It needs to be known, that the issue can be fixed as following, after restarting containerd / docker or the whole server:

univention-app reinitialize ucsschool-kelvin-rest-api
univention-app shell ucsschool-kelvin-rest-api /var/lib/univention-appcenter/apps/ucsschool-kelvin-rest-api/data/update_openapi_client
univention-app restart ucsschool-kelvin-rest-api

As this affects existing client environments, I changed this report from feature request to bug report with regression, as it was working before, broken during this update and waiting for an automated fix in other client environments not noticing the issue by their selfes.