Univention Bugzilla – Bug 56204
Installer stops at 92% when option to install available updates is enabled
Last modified: 2023-06-27 16:49:57 CEST
Created attachment 11077 [details] /var/log/univention/setup.log When selecting the option to install available updates during the installation process, the installation seems to never finish and stops at 92%. This is reproducible if using the "UCS: 5.0-3+e572" template in UVMM, I have a VM in that state and can provide access and logs.
Created attachment 11078 [details] ps axfu
Philipp analyzed the "upgrade after installation" behavior: * Primary will update to latest patch-level, e.g. $major.$minor-99 * If you setup a secondary UCS system (Backup,Replica,Member) and join it during installation: they will update maximum to the UCS version of the Primary * All other cases (unjoined) will update to latest available errata, but no patch-level update, e.g. $major.$minor-0. See univention-system-setup/scripts/90_postjoin/20upgrade https://git.knut.univention.de/univention/ucs/-/blob/5.0-4/base/univention-system-setup/usr/lib/univention-system-setup/scripts/90_postjoin/20upgrade So, on a primary it installs UCS 5.0-4 (+ errata upgrades?!) with the UMC unification. In the process overview we see the new UMC server running without any USS module process. The preup.sh of UCS 5.0-4 is killing existing UMC instances.
See also git:19f06b3744cc1ea7eae39290f060ba23275f05c7 Bug #55753 for a similar problem.