Bug 47247

Summary:	index: Adding the possibility to update LDAP indexes during LDAP schema updates
Product:	UCS	Reporter:	Sönke Schwardt-Krummrich <schwardt>
Component:	LDAP	Assignee:	UCS maintainers <ucs-maintainers>
Status:	NEW ---	QA Contact:	UCS maintainers <ucs-maintainers>
Severity:	normal
Priority:	P5	CC:	best, hahn, requate
Version:	UCS 5.0
Target Milestone:	---
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=47609 https://forge.univention.org/bugzilla/show_bug.cgi?id=33975 https://forge.univention.org/bugzilla/show_bug.cgi?id=41837
What kind of report is it?:	Feature Request	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):
Max CVSS v3 score:

Description Sönke Schwardt-Krummrich

2018-06-26 10:34:39 CEST

We recently had two cases where it would have made sense to automatically recreate (certain) LDAP indexes when updating LDAP schemas.
Case 1) concerned an OID collision and case 2) concerned a change in the object class hierarchies.
In both cases, incorrect search results can be expected after the LDAP schemes have been adapted. This then applies to all UCS-DCs that have to rebuild their indexes almost simultaneously (during/after schema replication).

Please note that the slapd must be switched off when reindexing and that the availability of executable LDAP servers in the domain could then become a problem if all system update their indexes "simultaneously".