Bug 47592

Summary: Allow examination of updater.log when a release update failed
Product: UCS Reporter: Dirk Wiesenthal <wiesenthal>
Component: UMC - Software updateAssignee: Dirk Wiesenthal <wiesenthal>
Status: CLOSED FIXED QA Contact: Ole Schwiegert <schwiegert>
Severity: normal    
Priority: P5    
Version: UCS 4.3   
Target Milestone: UCS 4.3-1-errata   
Hardware: Other   
OS: Linux   
What kind of report is it?: Feature Request What type of bug is this?: ---
Who will be affected by this bug?: --- How will those affected feel about the bug?: ---
User Pain: Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional):
Max CVSS v3 score:
Bug Depends on:    
Bug Blocks: 37223    

Description Dirk Wiesenthal univentionstaff 2018-08-15 13:46:00 CEST
After a release update failed (e.g., due to a PREUP check), the update is aborted. The user (hopefully) finds details in the updater.log. This file cannot be examined in UMC except during the very release update.

Suggestion: Parse /var/lib/univention-updater/univention-updater.status. If status=FAILED, allow opening the log file in the Updater module.
Comment 1 Dirk Wiesenthal univentionstaff 2018-08-15 13:47:24 CEST
Becomes particularly important when no log file is shown during release update ("Maintenance mode").
Comment 2 Dirk Wiesenthal univentionstaff 2018-08-15 14:03:54 CEST
Fixed in
  univention-updater 13.0.1-56A~4.3.0.201808151350

A warning is shown when the last release update failed. The UMC module then shows a "View log file" button which loads the last updater.log.

Two notes:
1. I decided to put the information in the rather unrelated "updater/maintenance_information" call. The reason is that I sometimes witnessed multiple updater module processes being created if too many UMCP commands were called at once.

2. On my machine, the updater.log rotated out before I finished the work on the bug. This led me to add a clumsy sentence about log rotation. Also, if this happens, UMC does not give the Administrator any chance of looking into the "correct" log file; this would have to be done on the terminal. Yet, my guess is that the new feature shows the log file of interest most of the times as the button should be clicked quickly after the update failed.
Comment 3 Ole Schwiegert univentionstaff 2018-08-22 10:38:34 CEST
Package installed: OK
Advisories&Changelog: OK
Possibility to view log in Updater Module: OK (*)

(*) There is no warning about log rotation in UMC. This messages got removed again.
Comment 4 Arvid Requate univentionstaff 2018-08-22 14:26:26 CEST
<http://errata.software-univention.de/ucs/4.3/210.html>