Bug 43168 – exam accounts aren't removed if no files are selected for distribution

Bug 43168 - exam accounts aren't removed if no files are selected for distribution


Summary:	exam accounts aren't removed if no files are selected for distribution

Status:	REOPENED

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

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

URL:
Keywords:

Depends on:
Blocks:	44157
	Show dependency tree / graph

Reported:	2016-12-12 10:17 CET by Florian Best
Modified:	2020-02-25 01:23 CET (History)
CC List:	1 user (show)

See Also:	31521
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?:	2: Will only affect a few 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.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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 Florian Best

2016-12-12 10:17:04 CET

If one starts an exam without distributing files (or remove them manually aka. Bug #31521) the ldap exam user objects aren't removed anymore when finishing the exam.

See
ucs-school-umc-exam/umc/python/schoolexam/__init__.py:
459 »   »   »   # delete exam users accounts
460 »   »   »   if project:
…
478 »   »   »   »   »   »   »   # remove LDAP user entry
479 »   »   »   »   »   »   »   connection.request('schoolexam-master/remove-exam-user', dict(

Comment 1 Sönke Schwardt-Krummrich

2019-02-05 21:43:27 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.