You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've a cluster with 10+ hosts and 60+ VMs. When I run the update, a lot of log is created. I would like to research more in the logfile (ultimate-updater.log), but everytime I do a run, it just logs 250 kB, 260 kB or sometimes 400 kB of data. The rest is just in my terminal window, but not in the logfile. I expected a log around 2 MB.
I'm using the terminal mode, not the WebUi.
To Reproduce
Steps to reproduce the behavior:
Type update in a terminal.
Debug output
In the terminal I could not find any error. Syslog is clean too. The log stopps in the middle of the output. For me it looks like, that the log appending is using a buffer and the last buffer is flushed, but no other anymore.
Expected behavior
A full log, like shown in the terminal.
Screenshots
None.
VM/LXC (please complete the following information):
Implemented in develop as commit c51c992a7c7cd11fcdabfaa9b4ccb82abb136845.
The update log cleanup no longer reads from and writes to the same log file through a live tee pipeline. The logging pipeline is closed and awaited before cleanup, ANSI removal uses a separate temporary file, and the cleaned log is replaced atomically while preserving ownership and permissions.
Regression coverage includes successful, warning, and error paths as well as output larger than 1 MB. Terminal output, exit codes, and existing update semantics remain unchanged.
Activity
Fix #387: preserve complete update logs
BassT23 commentedon Oct 30, 2026
Implemented in
developas commitc51c992a7c7cd11fcdabfaa9b4ccb82abb136845.The update log cleanup no longer reads from and writes to the same log file through a live
teepipeline. The logging pipeline is closed and awaited before cleanup, ANSI removal uses a separate temporary file, and the cleaned log is replaced atomically while preserving ownership and permissions.Regression coverage includes successful, warning, and error paths as well as output larger than 1 MB. Terminal output, exit codes, and existing update semantics remain unchanged.
The issue remains open for release tracking.