Univention Bugzilla – Bug 53321
Updater should go into maintenance mode after executing preup.sh
Last modified: 2021-06-09 16:06:22 CEST
When doing a release upgrade, the maintenance mode is started immediately. If the preup.sh script then aborts the upgrade, no notice is shown and one is redirected to the login dialog. After login in a notice is added saying that the upgrade failed, but one can easily oversee it. We should instead execute the preup.sh still in the updater module and show its output in a pop up - before starting the maintenance mode.
Would need a fix in 4.4-8
Unfortunately, executing the preup.sh (the "check" portion of it) is not reliable. We can postpone the maintenance mode for one call exactly. After that, the updater takes over. An exit code != 0 may be a false positive: Any errata update (and a 4.4-9 even more so) could fix a problem that would have prevented the update. If we stopped before installing all updates, we might decrease the usability instead of increasing it. There may be solutions for it, but the "customer space" in which a fix for this bug right here could actually shine may get very small. So small, that in fact we would not fix it at all.