Univention Bugzilla – Bug 39538
UCS@school installer is able to break the system
Last modified: 2023-06-23 14:15:24 CEST
The UCS@school installer runs it's tasks directly in the UMC module which causes that if the module dies the system is in an inconsistent state. The module could die for e.g. the following reasons: the client accidentally closes the browser, dpkg segfaults, the UMC-server crashes or get's restarted, etc. pp. The user even doesn't recognize that something failed as the progressbar runs forever with the same percent count (Bug #39537). She will detect that her system is broken if she aborts the installation and wants to relogin which was not possible in my case as the UMC-server has no +x flag anymore. The module should run its tasks e.g. via an AT-job.
This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 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.
*** Bug 31432 has been marked as a duplicate of this bug. ***
In other words: (In reply to Alexander Kläser from Bug #31432 comment #0) > Theoretically, it is currently possible that the installer module process is > being stopped, although the installation has not been finished. As the > initial "install" command request sends a response before the main > installation thread has been finished. If (a) the user closes the tab (i.e., > no progress information is requested) and (b) the installation procedure > endures longer than 10min (the module process timeout), the process can be > stopped before being really finished. > > This has been taken into account, e.g., in the exam module and could be > adapted in the installer, as well. I am not sure how probable the scenario > is.
This issue has been filed against UCS 4.4. UCS 4.4 is out of maintenance and UCS components may have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.