Univention Bugzilla – Bug 46440
Apps not updated during update to 4.3
Last modified: 2018-03-21 13:27:24 CET
See http://jenkins.knut.univention.de:8080/job/UCS-4.3/job/Apps/job/zimbra/job/App%20Autotest%20MultiEnv%20Release%20Update/SambaVersion=no-samba,Systemrolle=master/ At least for package based apps. The packages seemed to be upgraded during the update but the app registration for the new app version seems to be missing, 20_appcenter.19_app_version.test [2018-02-27 20:21:41.798102] zimbra: latest 1.1, installed 1.0 zimbra App 4.3 -> 1.1 zimbra App 4.2 -> 1.0
For Docker Apps, this should not be a problem because the App does not change. For Non-Docker Apps, it is missing because the App Center is not involved at all during the upgrade. The App should be registered correctly the first time the App Center module is opened. Alternatively, we call univention-app register --app during postup.sh.
The 4.3-0 postup contains univention-app update || true univention-app register --app || true This was introduced in bug #45328
Fixed by doing a "univention-app register --app" just before checking the status in the test scripts. This means that the status is actually broken right after the update. But it is way too much work to fix it in the App Center. The updater should better run postup.sh with version/version already set to 4.3 (Bug #46465). For now, we should consider putting "univention-app register --app" in the postinst of the very first errata update of univention-appcenter.
ok, test fixed, i tag this bug to 4.3-1
Fixed in univention-appcenter 7.0.1-29A~4.3.0.201803151413 Merely doing univention-app register --app in the postinst of univention-appcenter.
OK - update 4.3 master OK - update unjoined 4.3 slave OK - update 4.2-3 master with zimbra to 4.3 and errata -> app version correct OK - YAML
<http://errata.software-univention.de/ucs/4.3/2.html>