@host-> univention-upgrade --check Checking for package updates: none Checking for app updates: found @host -> univention-upgrade --noninteractive Checking for local repository: none Checking for package updates: none Checking for app updates: found The following apps can be upgraded: Horde Groupware Webmail Edition: The underlying container can be upgraded Starting app upgrade ERROR: app upgrade failed. Please check /var/log/univention/updater.log No app update, no release update, no nothing reason, the app update wants credentials (i think for a univention-run-join-script or something like that) but can't ask for them, because of --noninteractive and now the app upgrade in univention-upgrade thinks the best way to handle this situation is to abort the upgrade !? ...WARNING:univention.appcenter.actions.upgrade:Invalid credentials Invalid credentials ...WARNING:univention.appcenter.actions.upgrade:Invalid credentials Invalid credentials ...WARNING:univention.appcenter.actions.upgrade:Invalid credentials Too many failed attempts! ...WARNING:univention.appcenter.actions.upgrade:Too many failed attempts! Aborting... ...WARNING:univention.appcenter.actions.upgrade:Aborting... Solution, rename "--noninteractive" to "--abort-update" at least now it is clear what happens, no seriously, "--noninteractive" is used by customers and univention-upgrade should do its job even if that means that AppCenter joinscripts can't be executed
Fixed that one strongly in univention-updater 11.0.11-16.1502.201702171356 No error during App update will abort univention-upgrade. This includes asking for credentials with --noninteractive, but also everything else that can possibly go wrong. Advantage 1: If an App update goes wrong because of a bug fixed in 4.1-5 (but not in 4.1-4), the whole process may still succeed. Advantage 2: I do not need to check for --noninteractive and carefully test whether credentials will be needed down the road ... but may be substituted by the machine account? Just do it, and maybe the App can install without asking for credentials. Maybe you need to run the joinscripts afterwards.
Tests: It works and it makes sense. -------------------------------------------------------------------------- Checking for local repository: none Checking for package updates: none Checking for app updates: found The following apps can be upgraded: ownCloud 8.2: Version 8.2.6 can be upgraded to 8.2.9 Starting app upgrade Do you want to upgrade ownCloud 8.2 [Y|n]? File: /etc/univention/service.info/services/univention-appcenter.cfg File: /var/www/ucs-overview/entries.json ERROR: app upgrade failed. Please check /var/log/univention/updater.log Checking for release updates: found: UCS 4.1-4 Do you want to update to 4.1-4 [Y|n]? y Starting update to UCS version 4.1-4 [...] -------------------------------------------------------------------------- Code review: OK UCS 4.2 merge: OK YAML: OK
<http://errata.software-univention.de/ucs/4.1/407.html>