Bug 37084 – Exception if uidNumber or gidNumber out of range

Bug 37084 - Exception if uidNumber or gidNumber out of range


Summary:	Exception if uidNumber or gidNumber out of range

Status:	RESOLVED DUPLICATE of bug 37085

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 4.1-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-27 11:59 CET by Tim Petersen
Modified:	2020-11-19 18:59 CET (History)
CC List:	3 users (show)

See Also:	37083 52401
What kind of report is it?:	---
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?:	Yes
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 Tim Petersen

2014-11-27 11:59:27 CET

See https://forge.univention.org/bugzilla/show_bug.cgi?id=37083 - a reasonable exception would be nice.

Now you get "Failed to create LDAP object: noLock: : Typ war uidNumber".

Comment 1 Florian Best

2017-06-28 14:52:02 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 2 Stefan Gohmann

2019-01-03 07:15:22 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. 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 3 Florian Best

2019-02-06 11:43:52 CET


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