Univention Bugzilla – Bug 46062
backup2master: resolve_reference() too fuzzy
Last modified: 2023-12-12 11:10:40 CET
First comment contains customer information, here is an adjusted copy: https://git.knut.univention.de/univention/ucs/blob/4.3-0/management/univention-ldap/univention-backup2master#L75 -> resolve_reference() also finds references that are only similar to the hostname / FQDN of the UCS Master, nut no exact matches. This is quite dangerous, because backup2master suggests to change reference from a completely different server to the Backup (= new UCS Master). Example: Hostname of UCS Master: ucs Hostname of UCS Backup: backup1 Hostname of UCS Slaves: ucs-$SCHOOL Name of example school: abcdef > udm shares/share (attribute host) contains a reference to ucs in cn=share01,cn=shares,ou=abcdef,dc=example,dc=org > > Do you want this reference to be changed from > "ucs-abcdef.example.org" > to > "backup1-abcdef.example.org" > [Y|n|remove]? The script should only change references that exactly match the UCS Master. The current behaviour is very annoying and time-consuming especially in environments with a lot of UCS@school slaves that follow the naming scheme above.
Running `univention-backup2master` on "backup.master2backup.test" renamed the *domain* "master2backup" to "backup2backup"! [5.0-6] b7bfbca9a0 fix(backup2master): fix logic bugs doc/changelog/index.rst | 4 + management/univention-ldap/debian/changelog | 6 + management/univention-ldap/univention-backup2master | 533 ++++++++++++++++++---------------------- test/scenarios/base/backup2master.cfg | 145 +++++++++++ 4 files changed, 399 insertions(+), 289 deletions(-) Package: univention-ldap Version: 16.0.14-2 Branch: ucs_5.0-0 Scope: ucs5.0-6