Univention Bugzilla – Bug 50889
LDAP schema files that were not registered via ucs_registerLDAPExtension should be found in the diagnosis module
Last modified: 2020-03-11 14:42:07 CET
... and, preferrably, automatically registered.
Knowledge about schema files is hard coded. The following files are recognized: '/var/lib/univention-ldap/local-schema/univention-fetchmail.schema' '/var/lib/univention-ldap/local-schema/univention-openvpn.schema' '/var/lib/univention-ldap/local-schema/kopano4ucs.schema' '/var/lib/univention-ldap/local-schema/plucs.schema' '/var/lib/univention-ldap/local-schema/zarafa4ucs.schema' '/usr/share/univention-ldap/schema/asterisk4ucs.schema' '/var/lib/univention-ldap/local-schema/univention-corporate-client.schema' and registered via ucs_registerLDAPExtension with their appropriate App ID. For Kopano, Fetchmail, and OpenVPN4UCS, this differs as there are patches available and these differ in "$package" and "$packageversion". I took the correct ones there.
Done with umc/python/diagnostic/plugins/60_old_schema_registration.py in univention-management-console-module-diagnostic 5.0.1-47A~4.4.0.202003021527
7ed7df8c22 Bug #50889: add test 60_umc/35_umc_diagnostics_old_schema_registration
What i tested: installing the apps, deinstalling, upgrading to 4.4-3 unreleasd, run diagnostic module OK: paths to .schema files OK: packageversions OK: diagnostic module (texts, trigger, fix) OK: test 60_umc/35_umc_diagnostics_old_schema_registration OK: yaml -> verified
<http://errata.software-univention.de/ucs/4.4/476.html>