Bug 44120 – exam-users are recreated in the sync-to-ucs process in certain instances

Bug 44120 - exam-users are recreated in the sync-to-ucs process in certain instances


Summary:	exam-users are recreated in the sync-to-ucs process in certain instances

Status:	CLOSED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Exam mode
Version:	UCS@school 4.1 R2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS@school 4.2 vXXX
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:	44157
	Show dependency tree / graph

Reported:	2017-03-29 08:21 CEST by Jens Thorp-Hansen
Modified:	2023-06-12 15:39 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.103
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017032021000298
Bug group (optional):
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 Jens Thorp-Hansen

2017-03-29 08:21:32 CEST

If the exam is closed, but not all relevant S4-Connectors are done with the user replication, it is possible that exam-users are again created in the 
sync-to-ucs process.

Comment 1 Sönke Schwardt-Krummrich

2019-02-05 21:43:10 CET

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.