Bug 1413692

Summary:	custom schema is registered in small caps after schema reload.
Product:	Red Hat Enterprise Linux 6	Reporter:	German Parente <gparente>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED ERRATA	QA Contact:	Viktor Ashirov <vashirov>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.8	CC:	mlinden, nkinder, rmeggins, sramling, tbordaz, tlavigne
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-88.el6	Doc Type:	Bug Fix
Doc Text:	The fix for the bug 1144092 which was put in 389-ds-base-1.2.11.15-51.el6 and newer brought an side effect. The symptom is lowering the case of the reloaded new schema. This patch fixes the issue.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-21 10:24:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description German Parente 2017-01-16 16:50:32 UTC

Description of problem:


I am logging this bug because an important customer is having this difference in behavior even if this should not be considered as a bug:


1) copy a custom schema file to /etc/dirsrv/slapd-<server>/schema/

2) schema-reload.pl

3) ldapsearch .... -b "cn=schema" \*  attributetypes objectclasses


in releases till 50 we can see that the clauses MAY and MUST will show the attributetypes with the original case:

 MUST customAttr MAY ( customAttr2 $ customAttr3 $ ...

in releases after 50:

 MUST customattr MAY ( customattr2 $ customattr3 $ ...

A server restart will fix it.

I have detected that the problem comes from this patch:

https://fedorahosted.org/389/ticket/47973

removing it will show the attribute types in the original case.

even if this should not be a bug because the attribute types are case insensitive, as this is provoking issues for the customer, would it be possible to have a correction to show the same behavior ?

Thanks and regards,

German.

Comment 14 errata-xmlrpc 2017-03-21 10:24:43 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0667.html