Bug 42433

Summary: apt-get clean after successful (!) update
Product: UCS Reporter: Felix Botner <botner>
Component: Update - Release updatesAssignee: Felix Botner <botner>
Status: CLOSED FIXED QA Contact: Stefan Gohmann <gohmann>
Severity: normal    
Priority: P5 CC: gohmann
Version: UCS 4.1   
Target Milestone: UCS 4.1-4-errata   
Hardware: Other   
OS: Linux   
What kind of report is it?: Development Internal 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:

Description Felix Botner univentionstaff 2016-09-19 16:37:12 CEST
Currently, the package cache is cleaned during univention-upgrade (/usr/share/univention-updater/univention-updater net) before the update is started.

We should clean the cache after the update is finished successfully (postup).

Why?
If the update fails, the new sources.list list is removed. If univention-upgrade is restarted, the package cache is removed. Now one ends up with a half updated system unable to complete the upgrade unless manually adding apt sources for the new release.
Comment 1 Felix Botner univentionstaff 2017-02-21 17:04:25 CET
univention-updater r76922

call apt-get clean after successful update in univention-updater/python/univention-updater

merged to 4.2-0
staging/univention-updater.yaml r76923
Comment 2 Stefan Gohmann univentionstaff 2017-02-27 05:28:20 CET
Tests: OK, the packages are no longer removed before the update is started.

Code review: OK

4.2 merge: OK

YAML: OK
Comment 3 Janek Walkenhorst univentionstaff 2017-03-15 17:06:59 CET
<http://errata.software-univention.de/ucs/4.1/407.html>