Univention Bugzilla – Bug 43067
univention-system-setup-boot still installed after installation
Last modified: 2019-01-03 07:24:01 CET
We should consider removing univention-system-setup-boot in preup.sh if still installed and the system is already configured. There are still users out there with a broken setup and these users will run into problems during the update to 4.1-4 resp. the corresponding errata updates. http://forum.univention.de/viewtopic.php?t=6260&p=23413#p23413 +++ This bug was initially created as a clone of Bug #42808 +++ Happend in technical training on 8 machines and possibly on a customer system: http://forum.univention.de/viewtopic.php?f=56&t=6180 All machines in technical training have been installed via ISO on a USB stick. The debian installer and the webbased system setup part have been successfully gone through. But: network was not available during system setup part AND automatic update in the end of installation has been deselected. The systems seemed to be fine after installation and rebootet fine to commandline. Later on, the network connectivity was restored and univention-upgrade has been performed on command line. After reboot, univention system setup was shown ==> UCRV system/setup/boot/start was "true" I was able to reproduce this problem on a system installed without network access (ethernet interface was present, but no switch attached). I would bet that the script univention-system-setup/usr/lib/univention-system-setup/cleanup-post.d/90_remove_univention_system_setup_boot is the culprit. The following aptitude command seems to have failed or performed only half-way: aptitude -q -y markauto univention-system-setup-boot- \ univention-management-console-web-server \ univention-management-console-module-setup </dev/null When reproducing the problem, aptitude showed the status "id" (installed, marked for deletion) right before calling univention-upgrade → univention-system-setup-boot is still installed. # dpkg --get-selections univention-system-setup-boot univention-system-setup-boot install #
Stefan suggested to use use "ucr set --force system/setup/boot/start=false" at some point. I am not sure whether this could lead to problems at any point.
The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.