Univention Bugzilla – Bug 35022
univention-add-app registers ucs/web/overview variables even when not installing the app
Last modified: 2014-07-08 16:12:38 CEST
univention-add-app app_id $app_id --latest --master should install only the master packages of $app_id. These are normally UDM modules or LDAP schema extensions. But univention-add-app _always_ sets UCR variables for the UMC overview, so that (if $app_id defines an WebInterface) there is a link in ucs-overview leading to nowhere. univention-add-app is the "fallback" command suggested by us if backups are not reachable during installation. Maybe also used in some custom setups. Note that this is not really the fault of univention-add-app. app.register() does not provide an option to skip UCR registration
Do we have an app where it goes wrong?
Yes, a lot. Every app with WebInterface and DefaultPackagesMaster. This error may not be so common because one runs this command on DC Backups when an installation went wrong there. But potentially a lot of apps have this issue.
Fixed in univention-updater 9.0.41-2.1257.201406251547 The legacy call univention-add-app $component $pkg1 $pkg2 [...] is difficult to maintain. We should really consider removing it!
(In reply to Dirk Wiesenthal from comment #3) > Fixed in > univention-updater 9.0.41-2.1257.201406251547 > > The legacy call > > univention-add-app $component $pkg1 $pkg2 [...] > > is difficult to maintain. We should really consider removing it! I opened Bug 35279 for that.
In my tests I could verify, that an installation with --master will not anymore set UCR variables for the UCS overview package. However, when calling with --all (instead of --master), the variables are set correctly. YAML file → OK → VERIFIED
http://errata.univention.de/ucs/3.2/137.html