Bug 31432 – Module process could be stopped without being finished

Bug 31432 - Module process could be stopped without being finished


Summary:	Module process could be stopped without being finished

Status:	RESOLVED DUPLICATE of bug 39538

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Installer
Version:	UCS@school 3.0
Hardware:	Other Linux

Importance:	P5 normal with 2 votes (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-05-23 12:51 CEST by Alexander Kläser
Modified:	2019-02-06 09:46 CET (History)
CC List:	1 user (show)

See Also:	39537 39538 44076
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexander Kläser

2013-05-23 12:51:20 CEST

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.

Comment 1 Sönke Schwardt-Krummrich

2019-02-05 21:50:22 CET

This issue has been filled against UCS@school 3. The maintenance with
bug and security fixes for the last UCS@school version for UCS 3.x 
(→ UCS@school 3.2) has ended on Dec 31, 2016.

Customers still on UCS 3.x 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.

Comment 2 Florian Best

2019-02-06 09:46:16 CET


*** This bug has been marked as a duplicate of bug 39538 ***