Univention Bugzilla – Bug 47603
failed.ldif not purged on rejoin
Last modified: 2019-04-24 13:13:02 CEST
After a failed join a customer had to re-execute univention-join. The scripts checks for /var/lib/univention-directory-replication/failed.ldif only in line 214, but the OpenLDAP slapd is already started in line 546: /etc/init.d/slapd then finds the failed.ldif file an tries to apply it! Similar to Bug #41782 comment 19 the failed.ldif file should be detected early on and either be deleted or the script should abort.
Happened again. The failed.ldif still exists during rejoin, and causes the join to fail after hours.
a0547eeb02 Bug #47603: YAML a53a6e5939 Bug #47603: Remove failed.ldif early if exists Successful build Package: univention-join Version: 11.0.1-16A~4.4.0.201904161731 Branch: ucs_4.4-0 Scope: errata4.4-0 User: jbremer Host: dimma.knut.univention.de Logfile Path: /var/univention/buildsystem2/logs/ucs_4.4-0-0-errata4.4-0/univention-join_11.0.1-16A~4.4.0.201904161731.log.bz2 the failed.ldif will now be removed at the beginning of a join if it exists.
Verified: * Code review * Functional test * Advisory
<http://errata.software-univention.de/ucs/4.4/56.html>