Univention Bugzilla – Bug 33849
DefaultPackagesMaster may block release updates on DC Master
Last modified: 2023-03-25 06:46:22 CET
Slave installs app with DefaultPackagesMaster -> Master registers component, installs the master package -> App not marked as installed on master If a new release of UCS is available this (somewhat "hidden") repository may block the update to the new version on the master, although the app is installed on the slave. The error message is irritating, a correct fix would be an update of the app on the slave system. Note that this situation (DefaultPackagesMaster on a DC Master) may also lead to problems when there is a not backwards compatible cross update of UCS and the app (i.e. app_20140101 in UCS 3.1 ships a completely different schema package as app_20140101 in UCS 3.2). But this is unlikely to happen.
One way to solve this would be to remove DefaultPackagesMaster. Since UCS 3.2 the schema and other things could be registered via ucs_registerLDAPExtension.
Should not happen anymore, now that MasterRepositories are removed after installation of DefaultMasterPackages *** This bug has been marked as a duplicate of bug 33947 ***
Ok, can not happen anymore.