Univention Bugzilla – Bug 41236
Update to 4.1-2 is blocked due to Docker App Jenkins' repository enabled
Last modified: 2019-01-03 07:18:15 CET
The incorrect evaluation of the installation status of a Docker App may also cause a Repository to be included that should not. The Jenkins App does not really have a repository - and it should not be enabled as a component. Some bits of the App Center code in 4.1-0 and 4.1-1 without errata updates regard Jenkins as installed. Running /usr/sbin/univention-register-apps without a certain certain erratalevel will enable the jenkins component. This blocks any further updates (4.1-2, 4.2-0, ...). Unfortunately, this is done in an unpatched version of univention-system-setup-boot.postinst. So every new 4.1-0 and 4.1-1 installation (after the initial Jenkins release) is broken after system-setup. Workaround: 1. Install errata updates 2a. univention-app register 2b. (OR) Open App Center module As solution 2b exists, any actively used UCS system should at some point fix itself, yet there is no automatic fix. Fix could be 2a in either the postup.sh hook or univention-appcenter.postinst. +++ This bug was initially created as a clone of Bug #41009 +++ Old App Center code only goes over the DefaultPackages. This will always return True for Docker Apps like Jenkins and never for Docker Apps like OpenProject. This is a problem in _set_ucr_codes_variable. When installing a Non-Docker App (via old code), at the end Jenkins will be marked as installed in repository/app_center/installed
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.