Bug 50017 – Have more informative error messages when importing instead of traceback

Bug 50017 - Have more informative error messages when importing instead of traceback


Summary:	Have more informative error messages when importing instead of traceback

Status:	NEW

Product:	UCS@school
Classification:	Unclassified
Component:	Import scripts
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:
	Show dependency tree / graph

Reported:	2019-08-16 13:17 CEST by Christian Völker
Modified:	2020-04-22 08:03 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.069
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:	Yes
Ticket number:	2019081621000239
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.

Comment 1 Florian Best

2019-08-16 16:27:21 CEST

Maybe the question is more: Why was it possible that the same record-uid was used twice? I think this should be impossible from code perspective.
If we have errors in the code we probably should use the uniqeness overlay module that attribute, so that we don't get these invalid LDAP states.

Comment 2 Ingo Steuwer

2020-04-17 14:16:42 CEST

I reduce "who will be affected" as this seems to be rather unlikely to happen often