Univention Bugzilla – Bug 46850
preup.sh should check, if a failed.ldif exists
Last modified: 2018-05-16 17:04:24 CEST
In a customer environment the update to UCS 4.2 broke, because a failed.ldif exist and could not be applied. After fixing the failed.ldif, still an unconfigured slapd package was left behind, and the update could not be restarted. Maybe we can check for a failed.ldif in the preup script?
[4.3-0 575138c183] Bug #46850: check for failed.ldif in preup.sh [4.3-0 0d89c46be4] Bug #46850: YAML [4.3-0 f98772fd9a] Bug #46850: YAML I didn't add an ucr variable because moving the failed.ldif shouldn't be a problem if someone wants to ignore the error.
please make this change also to the current 4.3-0 preup.sh, there is no automatic way to change this file post release see https://forge.univention.org/bugzilla/show_bug.cgi?id=46669#c1
(In reply to Felix Botner from comment #2) > please make this change also to the current 4.3-0 preup.sh, there is no > automatic way to change this file post release > > see https://forge.univention.org/bugzilla/show_bug.cgi?id=46669#c1 Done. The new preup.sh should be signed and on the test mirror. After QA but before closing see: https://forge.univention.org/bugzilla/show_bug.cgi?id=46669#c3
OK, looks good
preup.sh is now on "updates.software-univention.de"
OK - https://updates.software-univention.de/ OK - update fails with existing failed.ldif OK - update starts without failed.ldif OK - signature OK - YAML
<http://errata.software-univention.de/ucs/4.3/40.html>