Bug #58318 introduced automatic adding of the univentionObjectIdentifier and a diagnostic module. In our CI tests we see that "univention-join/univention-server-join" creates e.g. DNS objects objects when attributes like dnsEntryZoneForward and dnsEntryZoneReverse and ip are set and those then don't have a univentionObjectIdentifier.
The diagnostic module for example shows (every Jenkins run every day): [dry-run] Updating univentionObjectIdentifier with entryUUID values. [dry-run] Would update 'relativeDomainName=slave,zoneName=ucs.test,cn=dns,dc=ucs,dc=test' | 'c9b6b3a0-ebeb-103f-963e-750a10220e05' [dry-run] Would update 'relativeDomainName=81.21,zoneName=207.10.in-addr.arpa,cn=dns,dc=ucs,dc=test' | 'c9bcbf3e-ebeb-103f-9645-750a10220e05' [dry-run] Would update 'relativeDomainName=backup,zoneName=ucs.test,cn=dns,dc=ucs,dc=test' | '97b19a96-ebf0-103f-9ac9-091f2f6ac5c4' [dry-run] Would update 'relativeDomainName=82.21,zoneName=207.10.in-addr.arpa,cn=dns,dc=ucs,dc=test' | '97b56af4-ebf0-103f-9acc-091f2f6ac5c4' [dry-run] Would update 'relativeDomainName=member,zoneName=ucs.test,cn=dns,dc=ucs,dc=test' | '12b8fd66-ebf5-103f-89df-5f42322f6fe5' [dry-run] Would update 'relativeDomainName=83.21,zoneName=207.10.in-addr.arpa,cn=dns,dc=ucs,dc=test' | '12be9d8e-ebf5-103f-89e2-5f42322f6fe5' [dry-run] Updated 6 records. And we have a PS/customer report about: dn: univentionAppID=radius_9.0,cn=radius,cn=apps,cn=univention,dc=dev,dc=ucs,dc=example,dc=org in a non-mixed environment.
The license object doesn't have univentionObjectType either.
The Jenkins test for the recyclebin revealed that there are also objects in the S4/AD Connector not having univentionObjectIdentifier. But they didn't show which ones.
I noticed the problem mentioned in the inital bug report in the training environment (after installation of univention-demodata). It as appears as if DNS-objects in general do not get the univentionObjectIdentifier. root@dn1:~# univention-run-diagnostic-checks -t 58_univentionObjectIdentifier Executing following checks: ['58_univentionObjectIdentifier'] You can find the logging messages of the diagnostic modules at /var/log/univention/management-console-module-diagnostic.log ran 58_univentionObjectIdentifier successfully. root@dn1:~# udm computers/windows create --position "cn=computers,"$ldap_base"" --set name=w2 --set network="cn=default,cn=networks,"$ldap_base"" Object created: cn=w2,cn=computers,dc=training,dc=ucs root@dn1:~# univention-run-diagnostic-checks -t 58_univentionObjectIdentifier Executing following checks: ['58_univentionObjectIdentifier'] You can find the logging messages of the diagnostic modules at /var/log/univention/management-console-module-diagnostic.log ############################################## Start 58_univentionObjectIdentifier ############################################## ## Check failed: 58_univentionObjectIdentifier - Validierung, dass alle Objekte den Univention Object Identifier gesetzt haben ## Alle Objekte der Klasse "univentionObject" sollten das Attribut "univentionObjectIdentifier" tragen in OpenLDAP. [dry-run] Updating univentionObjectIdentifier with entryUUID values. [dry-run] Would update 'relativeDomainName=w2,zoneName=training.ucs,cn=dns,dc=training,dc=ucs' | 'abbba5e8-6edd-1040-9e85-b70369bce80e' [dry-run] Would update 'relativeDomainName=114,zoneName=0.0.10.in-addr.arpa,cn=dns,dc=training,dc=ucs' | 'abbcd2ce-6edd-1040-9e88-b70369bce80e' [dry-run] Updated 2 records. ############################################### End 58_univentionObjectIdentifier ############################################### root@dn1:~# univention-app info UCS: 5.2-4 errata298 Installed: cups=2.4.2 dhcp-server=16.0 samba4=4.21 Upgradable: For me this rather looks more than a bug than a feature request, affecting most installed domains.
Another customer has issues regarding this: After applying DNS settings at a computer object, the corresponding network objects beneath cn=dns and cn=dhcp are created without the attribute univentionObjectIdentifier, which results in diagnostic warning messages. Because we warn the user about those objects, we should create the objects correctly. Therefore I changed this from feature -> bug.