Cleanup legacy UDM/LDAP showed no auxiliary entries, but there were some

[boospy]

Based on this article, I cleaned up legacy entries in LDAP.

Remove legacy UDM / LDAP objects with upgrade to UCS-5.2

With UCS-5.2 several legacy Univention Directory Manager (UDM) modules have been removed. Previously they were used to manage certain entries in LDAP, which become unmanageable after the upgrade: The data remains stored in LDAP, but the modules to create / show / modify / move / delete them is no longer available. In many cases this is unproblematic, but leads to long-term problems as folders containing such objects become un-removable, un-movable or un-renamable. Therefore those entries should…

 The following objects are no longer supported with UCS 5.2:

               dn: cn=24x7,cn=nagios,dc=party,dc=lan
               dn: cn=WorkHours,cn=nagios,dc=party,dc=lan
               dn: cn=NonWorkHours,cn=nagios,dc=party,dc=lan

       They must be removed before the update can be done.

But then the following appeared when I pressed remove:

 bash check.sh delete_legacy_objects

Starting check.sh (Do 13. Mär 18:44:18 CET 2025):

Removing structural objects

(structuralObjectClass=univentionNagiosTimeperiodClass)
Removing auxiliary data
(objectClass=univentionVirtualMachineGroupOC)
(objectClass=univentionVirtualMachineHostOC)

The auxiliary entries were not visible in the first output. Is that normal?

The “VirtualMaschine” feature was never used.

Does it matter then? (Hopefully not)

[Best]

No, doesn’t matter if they UVMM was never installed.

Command for removing the Nagios Timeperiods:
univention-ldapsearch -LLL 'objectClass=univentionNagiosTimeperiodClass' 1.1 | sed -rne 's#^dn: ##p' | while read -r dn; do udm nagios/timeperiod remove --dn "$dn" || ldapdelete -D "cn=admin,$(ucr get ldap/base)" -y /etc/ldap.secret "$dn"; done

must be executed as root user on the primary server!

[boospy]

Sorry for the late reply. It has worked. The normal check command give me this output:

Starting ./check.sh (Sa 10. Mai 15:08:33 CEST 2025):
Checking auth_faillog ...                         OK
Checking blocking_apps ...                        OK
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
Checking verify_translog_schema ...               OK

If i say: “./check.sh delete_legacy_objects” I get this:

Starting ./check.sh (Sa 10. Mai 15:09:34 CEST 2025):
> Removing structural objects
>> (structuralObjectClass=univentionNagiosTimeperiodClass)
> Removing auxiliary data
>> (objectClass=univentionVirtualMachineGroupOC)
>> (objectClass=univentionVirtualMachineHostOC)

But I assume that this is normal and okay in this case? Because every check is confirmed with “OK” at the top.