Bug 39409 – Automatic displayName update leads to tracebacks in UCS@school environments

Bug 39409 - Automatic displayName update leads to tracebacks in UCS@school environments


Summary:	Automatic displayName update leads to tracebacks in UCS@school environments

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	UMC - Users
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-3-errata
Assigned To:	Sönke Schwardt-Krummrich
QA Contact:	Daniel Tröder

URL:
Keywords:

Depends on:	38385
Blocks:
	Show dependency tree / graph

Reported:	2015-09-25 22:01 CEST by Sönke Schwardt-Krummrich
Modified:	2015-11-04 17:26 CET (History)
CC List:	3 users (show)

See Also:
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?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	External feedback
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 Sönke Schwardt-Krummrich

2015-09-25 22:01:12 CEST

Ticket 2015092421000514 describes a traceback in the S4 connector log, that is caused by the introduction of the automatic displayName update.
The LDAP modlist is not correctly created by users/user.py so the S4 connector on school slaves fail to update the displayName during sync S4→UCS.

+++ This bug was initially created as a clone of Bug #38385 +++

Comment 1 Sönke Schwardt-Krummrich

2015-09-25 22:23:44 CEST

The old code contained the line 
     ml.append(('displayName', 
                self.oldinfo.get('displayName', [''])[0], 
                new_displayName))
to replace the old value with a new displayName value. Unfortunately, self.oldinfo['displayName'] is always of type string, so the code tries to replace an invalid old_value: e.g.
   ('displayName', 'S', 'Service')

This has now been fixed.

univention-directory-manager-modules (10.0.31-17):
r63999 | Bug #39409: fixed automatic update of displayName

ucs-test (5.0.171-11):
r64000 | Bug #39409: improved 28_displayName_update

2015-09-09-univention-directory-manager-modules.yaml:
r64002 | Bug #39409: updated YAML
r64001 | Bug #39409: updated YAML

I was not able to reproduce the problem with the ucs-test script. Even after adding an additional test that only sets the lastname and leaves the firstname empty.

Within the customer environment, the problem only occurred if only a lastname was specified at the user object.

Comment 2 Sönke Schwardt-Krummrich

2015-09-27 22:19:17 CEST

Merged changes of bugs #38385, #39292 and #39409 to UCS 4.1-0 (yes, they were all missing :-()
→ r64019 | Bug #38385, #39292, #39409: automatic update of displayName
→ r64021 | Bug #39409: improved 28_displayName_update
→ r64020 | Bug #38385: added 28_displayName_update

Comment 3 Sönke Schwardt-Krummrich

2015-10-06 12:47:37 CEST

Missing rebuild of univention-directory-manager-modules for UCs 4.1-0 has been  catched up: package version is 11.0.2-1.1345.201510061159

Comment 4 Daniel Tröder

2015-10-08 16:08:35 CEST

OK: code
OK: manual test
OK: automatic test (ucs-test_5.0.172-2.1243.201510070957): # /usr/share/ucs-test/61_udm-users/28_displayName_update -f
OK: YAML

Comment 5 Janek Walkenhorst

2015-11-04 17:26:43 CET

<http://errata.software-univention.de/ucs/4.0/357.html>