Univention Bugzilla – Bug 48697
Adopt installer behaviour to samba installation simplifications
Last modified: 2019-03-12 11:01:11 CET
Now that the installation simplifications have been implemented, the UCS@school installer must also be slightly adapted. Expected behavior: DC master: → no changes should be necessary here DC backup: → during the installation, the role package of the backup should be installed in addition to the list of current packages ("ucs-school-master" or "ucs-school-singlemaster"?) → add "ucs-school-backup" to the list of packages to be installed DC slave (central): → when the UMC module is opened, the package "ucs-school-central-slave" is recognized as installed, the UCS@school installer should indicate that UCS@school has been installed correctly and no further steps are necessary (similar to on the master). References to local UMC modules should not be displayed. If necessary, a hint is given that the administration of UCS@school takes place on the master. → If neither "ucs-school-slave" nor "ucs-school-nonedu-slave" nor "ucs-school-central-slave" is installed, the installer should "offer" the installation of "ucs-school-central-slave". The installer must not ask for an OU or similar questions, but only point out that all required information is already available. DC slave (school): → no changes should be necessary here Memberserver: → no changes should be necessary here
After discussion the changes on DC backup are not necessary anymore. Also the installer behavior shall not change. This means if the installer finds a slave without any role packages installed it defaults to installing the educational school slave
Package: ucs-school-umc-installer Version: 7.0.0-4A~4.4.0.201902211449 Branch: ucs_4.4-0 Scope: ucs-school-4.4 The installer now recognizes the configured central slave.
(In reply to Ole Schwiegert from comment #2) > The installer now recognizes the configured central slave. → OK (In reply to Ole Schwiegert from comment #1) > After discussion the changes on DC backup are not necessary anymore. → OK > Also the installer behavior shall not change. This means if the installer > finds a slave without any role packages installed it defaults to installing > the educational school slave I can think of the following situations: 1) system is unjoined and univention-join is called → join hook installs UCS@school installer AND metapackage → if UCS@school installer is started afterwards, it recognized the metapackage and shows the hint, that UCS@school has been successfully installed and configured. 2) system is joined, UCS@school is NOT installed → UCS@school is installed on DC master and therefore also the join hook → UCS@school app is manually installed on a DC backup/DC slave via Univention App Center → after installation, the App Center automatically calls univention-run-join-scripts which triggers the join hook and installs the UCS@school metapackage → if UCS@school installer is started afterwards, it recognized the metapackage and shows the hint, that UCS@school has been successfully installed and configured. 3) system is joined, UCS@school installer is installed, but not configured → UCS@school is installed on DC master and therefore also the join hook → if now the UCS@school installer is selected, it will offer - on a DC backup the installation of ucs-school-master resp. ucs-school-singlemaster - on a DC slave the wizard to specify a OU name (old slave installation behaviour) I think, this is ok for now, because it enabled us to use scenario 3) as a fallback, if 1) and 2) did not work and 3) is (hopefully) a rather rare situation. OK: code change OK: functional change OK: manual tests
UCS@school 4.4 v1 has been released. https://docs.software-univention.de/release-notes-ucsschool-4.4v1-de.html If this error occurs again, please clone this bug.