Univention Bugzilla – Bug 47436
Updating a patchlevel during system-setup will abort system-setup when an erratum restarts UMC
Last modified: 2019-03-15 22:52:49 CET
During system setup we disable the restart of UMC, because umc-server starts setup-join.sh in a subprocess. When the checkbox to install updates during system setup is checked, we install all available patchlevel updates. But in univention-updater postup.sh we explicitely enable UMC restart again with /usr/share/univention-updater/enable-apache2-umc. This will cause system-setup to abort when an erratum in the next patchlevel exists that restarts UMC-server. System-setup hook and cleanup scripts will not be called, so the system is in an undefined state. The bug is also relevant for App Appliances which are not the latest patchlevel. Our UCS Appliances are usually on the latest patchlevel. To reproduce, one can install from UCS 4.3-0 and update to 4.3-1 during system setup. A real fix would be to make setup-join.sh not a child process of umc-server, but start it independently. Workaround is to uncheck the 'update system' option in system setup.
(In reply to Erik Damrose from comment #0) > When the checkbox to install updates during system setup is checked, we > install all available patchlevel updates. But in univention-updater > postup.sh we explicitely enable UMC restart again with > /usr/share/univention-updater/enable-apache2-umc. Maybe we can simply check in postup.sh if the update has been started through system setup?
e3bc45ad univention-updater No package rebuild, as it is just a postup change. In postup.sh, do not reenable apache2 and UMC restarts, when system-setup is running. System-setup will reenable it at the end of the setup. I copied the signed postup.sh to the testing and test_mirror. In a test install with 4.3-0, the update to 4.3-1 was done, and system setup completed successfully.
!
I fixed the logic error in 78c8ff962 and updated the file on both test mirrors
OK, release
published on external mirror
OK