Our pre-update checks block upgrades to UCS 5.1 and 5.2 if a specific app is not available for UCS 5.2. However, the error message appears even when the app is available for UCS 5.2. This likely occurs due to the logic within the check itself. The issue seems to be that a UCS 5.0-10 system cannot retrieve the necessary app metadata for UCS 5.2. As a result, the check falsely identifies an error and prevents the update. Since the metadata that can be accessed depends on the current UCS version, a system running UCS 5.0-10 only receives information relevant to that version. Consequently, the update to UCS 5.2 cannot proceed through the standard process. I think it would be best to adapt the code for pre-up-check for UCS 5.1 and UCS 5.2. UCS Version: UCS: 5.0-10 errata1257 Installed: apple-school-manager=3.0.3 ucsschool=5.0 v7 Upgradable: Message from the per-up-check: blocking_apps: The update to 5.2 is currently not possible, because the following Apps are not available for UCS 5.2: Code from the per-up-check: # check if apps are available update_check_blocking_apps () { local var="update$VERSION/ignore_blocking_apps" ignore_check "$var" && return 100 [ -f /var/univention-join/joined ] || return 0 univention-app update-check --ucs-version "${VERSION_NAME}" univention-app update Downloading "https://appcenter.software-univention.de/meta-inf/app-categories.ini"... Downloading "https://appcenter.software-univention.de/meta-inf/rating.ini"... Downloading "https://appcenter.software-univention.de/meta-inf/license_types.ini"... Downloading "https://appcenter.software-univention.de/meta-inf/ucs.ini"... Downloading "https://appcenter.software-univention.de/meta-inf/suggestions.json"... Downloading "https://appcenter.software-univention.de/meta-inf/5.0/all.tar.gpg"... Downloading "https://appcenter.software-univention.de/meta-inf/4.4/all.tar.gpg"... Downloading "https://appcenter.software-univention.de/meta-inf/4.3/all.tar.gpg"... ucr search --brief version appcenter/apps/apple-school-manager/version: 3.0.3 appcenter/apps/ucsschool/version: 5.0 v7 notifier/protocol/version: 3 repository/mirror/version/end: <empty> repository/mirror/version/start: <empty> repository/online/component/.*/version: <empty> repository/online/component/apple-school-manager_20240508141833/version: current repository/online/component/ucsschool_20250204171805/version: current version/erratalevel: 1257 version/patchlevel: 10 version/version: 5.0
apple-school-manager is not update-available for 5.2. 5.0 apple-school-manager_20240508141833.ini -> OK 5.1 apple-school-manager_20240508141833.ini -> OK 5.2 apple-school-manager_20250318153240.ini -> Does not match apple-school-manager_20250324113725.ini -> Does not match => You cannot update. We need the same timestamps (= "component_id") in all UCS versions (apple-school-manager_20240508141833). In 5.0, there is already a new version apple-school-manager_20250430142420.ini -> This needs to be the same in 5.1 and 5.2 as well. See also https://help.univention.com/t/how-to-make-your-application-available-on-ucs-5-2/23885
Another customer affected 2025041721000198 The system can not be updated to UCS 5.2 due to the following reasons: blocking_apps: The update to 5.2 is currently not possible, because the following Apps are not available for UCS 5.2: * Print server (CUPS) * Let's Encrypt * UCS Dashboard Client * Active Directory-compatible Domain Controller * Self Service * Self Service Backend * UCS@school
(In reply to Dirk Wiesenthal from comment #1) > apple-school-manager is not update-available for 5.2. > > 5.0 apple-school-manager_20240508141833.ini -> OK > 5.1 apple-school-manager_20240508141833.ini -> OK > 5.2 apple-school-manager_20250318153240.ini -> Does not match > apple-school-manager_20250324113725.ini -> Does not match > > => You cannot update. We need the same timestamps (= "component_id") in all > UCS versions (apple-school-manager_20240508141833). > > In 5.0, there is already a new version > apple-school-manager_20250430142420.ini -> This needs to be the same in 5.1 > and 5.2 as well. > > See also > https://help.univention.com/t/how-to-make-your-application-available-on-ucs- > 5-2/23885 This is something the app provider has to do, right, this is nothing we (support) can do for the customer. So who will do that and who reaches out to the app provider regarding this?
So has this to do with the SupportedUcsVersions in the ini? Like this: Then we also do this not properly since 5.0: root@primary:~ # grep -E SupportedUcsVersions /var/cache/univention-appcenter/appcenter.software-univention.de/5.0/ucsschool*.ini /var/cache/univention-appcenter/appcenter.software-univention.de/5.0/ucsschool_20201208103021.ini:SupportedUcsVersions = /var/cache/univention-appcenter/appcenter.software-univention.de/5.0/ucsschool_20220713122521.ini:SupportedUcsVersions = /var/cache/univention-appcenter/appcenter.software-univention.de/5.0/ucsschool_20220727135154.ini:SupportedUcsVersions = /var/cache/univention-appcenter/appcenter.software-univention.de/5.0/ucsschool_20230802094418.ini:SupportedUcsVersions = /var/cache/univention-appcenter/appcenter.software-univention.de/5.0/ucsschool_20240318112841.ini:SupportedUcsVersions = /var/cache/univention-appcenter/appcenter.software-univention.de/5.0/ucsschool_20240924121830.ini:SupportedUcsVersions = /var/cache/univention-appcenter/appcenter.software-univention.de/5.0/ucsschool_20250204171805.ini:SupportedUcsVersions =
We maintain the app and somehow the component id for the app version we released in 5.2 is wrong. During testing the component id was documented and matched, so we are not entirely sure how the component id changed. I will take this with me to our daily on Friday and see if we can fix this ASAP.
Thank you very much for the quick feedback, it would be very good if we could fix this as soon as possible regarding the apple-school-manager. However, I would like to make it clear that this bug is not just about the apple-school-manager application, because in another ticket which I have linked, another customer was unable to update his system because the following apps blocked the update, but all the apps displayed are available for 5.2. (In reply to Mirac Erdemiroglu from comment #2) > Another customer affected 2025041721000198 > > The system can not be updated to UCS 5.2 due to the following reasons: > > blocking_apps: > The update to 5.2 is currently not possible, > because the following Apps are not available for UCS 5.2: > * Print server (CUPS) > * Let's Encrypt > * UCS Dashboard Client > * Active Directory-compatible Domain Controller > * Self Service > * Self Service Backend > * UCS@school
We released 5.0.2 of the Apple School Manager for UCS 5.2, which should solve the problem for this app. Sorry for the inconvenience. The component id got changed during the implementation of our automated app release procedure.
Another customer affected 2025042821000195 The update to 5.2 is currently not possible, because the following Apps are not available for UCS 5.2: * Windows-compatible Memberserver
Another customer affected 2025041021000165 blocking_apps: The update to 5.2 is currently not possible, because the following Apps are not available for UCS 5.2: * Active Directory Connection * Admin Diary Backend * Admin Diary Frontend * Windows-compatible Memberserver * Self Service * Self Service Backend
Same Problem with update Kelvin REST API, Ticket 2025052621000062 (already linked). In the Univention Forum is also a discussion about this, with a various number of applications affected, see: https://help.univention.com/t/available-applications-in-ucs-5-2/23859
We have tried to reproduce the mentioned problem with most of the apps mentioned and could not identify any app that should block the upgrade. Is it possible to access a system, where the upgrade does not work and investigate? We suspect that the shown error is masking another underlying problem, possibly related to networking and/or caching problems. We are going to investigate locally as well, by code review and trying to reproduce the error somehow with other factors. One more question: In the cases where the update was denied due to blocked apps, is it possibly the case that *all* apps installed on the system were marked as blocking?
Ticket 2025041021000165 From the updater.log. Starting univention-upgrade. Current UCS version is 5.1-0 errata0 Checking for package updates: none Checking for app updates: none Checking for release updates: found: UCS 5.2-0 Please rerun command without --check argument to install. Starting ./check.sh (Mi 9. Apr 23:54:36 CEST 2025): Checking auth_faillog ... OK Checking blocking_apps ... Unable to cache apps Unable to cache apps FAIL Checking disk_space ... OK Checking docker_storage_driver ... OK Checking failed_ldif ... OK Checking for_postgresql96 ... OK Checking hold_packages ... OK Checking keycloak_migration ... OK Checking ldap_connection ... OK Checking ldap_schema ... OK Checking legacy_objects ... OK Checking master_version ... OK Checking min_version ... OK Checking minimum_ucs_version_of_all_systems_in_domain ... OK Checking openldap_bdb ... OK Checking overwritten_umc_templates ... OK Checking package_status ... OK Checking role_package_removed ... OK Checking selinux_deactivated ... OK Checking slapd_on_member ... OK Checking system_date_too_old ... OK Checking user_country_mapping ... OK Checking valid_machine_credentials ... OK The system can not be updated to UCS 5.2 due to the following reasons: blocking_apps: The update to 5.2 is currently not possible, because the following Apps are not available for UCS 5.2: * Active Directory Connection * Admin Diary Backend * Admin Diary Frontend * Windows-compatible Memberserver * Self Service * Self Service Backend
Both Dirk and Ole tried to reproduce the error unsuccessfully. They are certain that the underlying problem is not a missing compatibility of the listed apps, but instead some sort of error in the App center that creates false positives. How the App center ends up in this state is currently unclear, but it will not happen for most customers. I therefore reduce the user pain calculation fields to reflect these new insights. If this arises at a customer, please do contact Dirk and me, so Dirk can take a look at the specific affected environment.
univention-updater (17.0.34-1) dfc5c661002e | fix(univention-updater): disabling blocking_apps for 5.2
Fix the path directory were the appcenter store the cache for the next release during an upgrade. Successful build Package: univention-appcenter Version: 11.2.0 Branch: 5.2-0 Scope: errata5.2-2
Tests: OK Code review: OK YAML: OK
<https://errata.software-univention.de/#/?erratum=5.2x149>
The issue seemingly still occurs, e.g. with OPSI. Opsi in the 5.2 repository: https://appcenter.software-univention.de/univention-repository/5.2/maintained/component/opsi_20250321373225/ https://appcenter.software-univention.de/univention-repository/5.2/maintained/component/opsi_20250604391845/ Checking for release updates: The update to UCS 5.1-0 is blocked because the component 'opsi_20250604391845' is marked as required. none Setting update/available
The version of opsi with the component id opsi_20250604391845 was not released for the 5.1 Appcenter which caused the problem. Tt was fixed with the release of version 4.3.0.51-ucs2.