Thanks a lot! Please find below the output of the update script:
Starting pre-update-checks-5.2-0 (2026. szept. 30., szerda, 10:03:31 CEST):
Checking auth_faillog … OK
Checking blocking_apps … OK
Checking disk_space … OK
Checking docker_storage_driver … OK
Checking failed_ldif … OK
Checking for_postgresql96 … FAIL
Checking hold_packages … OK
Checking keycloak_migration … FAIL
Checking ldap_connection … OK
Checking ldap_schema … OK
Checking legacy_objects … FAIL
Checking master_version … OK
Checking mdb_max_size … 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 … FAIL
Checking valid_machine_credentials … OK
Checking verify_translog_schema … OK
The system can not be updated to UCS 5.2 due to the following reasons:
user_country_mapping:
Users in LDAP need to be migrated so their “country” property is stored
in the correct LDAP attribute “c” instead of in the state (“st”).
UCS 5.0 supported both configurations. With UCS 5.2 only the correct mapping
is supported. A migration is necessary before upgrading.
The migration can be performed using the command
/usr/share/univention-directory-manager-tools/udm-remap-country-from-st-to-c
or using the UMC module "System diagnostic".
keycloak_migration:
Starting with UCS 5.2 the Keycloak app replaces SimpleSAMLphp
and the Kopano Konnect app as the default identity provider in UCS.
Before the update to 5.2 can start, this domain has to be migrated
to Keycloak.
This migration has not happend yet!
Please read the UCS 5.2 release notes <https://docs.software-univention.de/release-notes/5.2-0/en/index.html>
and the Keycloak migration guide: <https://docs.software-univention.de/keycloak-migration/index.html>
for how to migrate your domain to Keycloak.
- The following old SimpleSAMLphp/Kopano Konnect objects have been found.
They need to be removed before the update can happen:
* SAMLServiceProviderIdentifier=google.com,cn=saml-serviceprovider,cn=univention,dc=titkarsag,dc=mta,dc=hu
* SAMLServiceProviderIdentifier=https://sp.testshib.org/shibboleth-sp,cn=saml-serviceprovider,cn=univention,dc=titkarsag,dc=mta,dc=hu
* SAMLServiceProviderIdentifier=https://saml.salesforce.com,cn=saml-serviceprovider,cn=univention,dc=titkarsag,dc=mta,dc=hu
* SAMLServiceProviderIdentifier=https://cloud.titkarsag.mta.hu/univention/saml/metadata,cn=saml-serviceprovider,cn=univention,dc=titkarsag,dc=mta,dc=hu
* SAMLServiceProviderIdentifier=https://cloud.titkarsag.mta.hu/nextcloud/apps/user_saml/saml/metadata,cn=saml-serviceprovider,cn=univention,dc=titkarsag,dc=mta,dc=hu
Migration to Keycloak incomplete, update to UCS 5.2 not possible
Checking Keycloak migration status ...
- ucs/server/sso/uri (None) exists or is not relevant
for_postgresql96:
WARNING: PostgreSQL-9.6 is no longer supported by UCS-5.2 and must be migrated to
a newer version of PostgreSQL. See Updating from PostgreSQL 9.6 or 9.4 to PostgreSQL 11 for
more details.
This check can be disabled by setting the UCR variable 'update52/ignore_postgresql96' to 'yes'.
But be aware that this is not recommended!
legacy_objects:
The following objects are no longer supported with UCS 5.2:
dn: cn=24x7,cn=nagios,dc=titkarsag,dc=mta,dc=hu
dn: cn=WorkHours,cn=nagios,dc=titkarsag,dc=mta,dc=hu
dn: cn=NonWorkHours,cn=nagios,dc=titkarsag,dc=mta,dc=hu
They must be removed before the update can be done.
See <https://help.univention.com/t/22252> for details.
This check can be disabled by setting the UCR variable 'update52/ignore_legacy_objects' to 'yes'.