#48936 Duplicate collation entries
Closed: Fixed None Opened 2 years ago by nhosoi.

Description of problem:

Desktop LDAP clients have trouble accessing FreeIPA via LDAP.
GQ crashes when accessing objects. Can display object hierarchy and schema but
fails as soon as it accesses and object (leaf).
Luma can access and display objects but reports many errors:
ERROR: [base.backend.ObjectClassAttributeInfo/MainThread]: Could not fetch LDAP
schema from server. Reason:
NAME not unique for ( 2.16.840.1.113730.3.3.2.211.1 NAME
'caseIgnoreOrderingMatch-sk' DESC 'sk' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )


Version-Release number of selected component (if applicable):

freeipa-admintools-4.3.1-1.fc24.noarch
freeipa-common-4.3.1-1.fc24.noarch
freeipa-server-common-4.3.1-1.fc24.noarch
freeipa-client-common-4.3.1-1.fc24.noarch
freeipa-client-4.3.1-1.fc24.x86_64
freeipa-server-4.3.1-1.fc24.x86_64
389-ds-base-libs-1.3.5.10-1.fc24.x86_64
389-ds-base-1.3.5.10-1.fc24.x86_64


How reproducible:

Always.


Steps to Reproduce:
1. Install freeipa and create instance.
2. Access the LDAP service using a desktop client.


Actual results:

See above.


Expected results:

Should work.


Additional info:

My FreeIPA instance started life some time ago and has been upgraded a number
of times so I tried a new VM installation and it has exactly the same issue.
That implies that it is not an upgrade issue.

Since GQ can see the schema tree I used that. It shows some duplicate entries
under {server}/matchingRules:

Name                            OID
...
caseIgnoreOrderingMatch-sk      2.16.840.1.113730.3.3.2.42.1
caseIgnoreOrderingMatch-sk      2.16.840.1.113730.3.3.2.211.1
caseIgnoreOrderingMatch-sl      2.16.840.1.113730.3.3.2.43.1
caseIgnoreOrderingMatch-sl      2.16.840.1.113730.3.3.2.212.1
caseIgnoreOrderingMatch-sq      2.16.840.1.113730.3.3.2.44.1
caseIgnoreOrderingMatch-sq      2.16.840.1.113730.3.3.2.213.1
...

It looks like these languages are being added twice.
All other entries are unique (I think).

Just guessing but the probable cause is:
https://git.fedorahosted.org/cgit/389/ds.git/tree/ldap/schema/slapd-collations.
conf#n58
https://git.fedorahosted.org/cgit/389/ds.git/tree/ldap/schema/slapd-collations.
conf#n59
https://git.fedorahosted.org/cgit/389/ds.git/tree/ldap/schema/slapd-collations.
conf#n61
then:
https://git.fedorahosted.org/cgit/389/ds.git/tree/ldap/schema/slapd-collations.
conf#n227
https://git.fedorahosted.org/cgit/389/ds.git/tree/ldap/schema/slapd-collations.
conf#n228
https://git.fedorahosted.org/cgit/389/ds.git/tree/ldap/schema/slapd-collations.
conf#n229

I think the second batch of entries is for sub-languages but they also appear
to add the main language too which is defined in the first batch.

Commit?
https://git.fedorahosted.org/cgit/389/ds.git/commit/ldap/schema/slapd-collation
s.conf?id=e0c78d5b87d4d798a936eba9c90f5db5347bcb3c

{{{
192 collation id "" "" 1 3 2.16.840.1.113730.3.3.2.176.1 id-ID
193 collation id ID "" 1 3 2.16.840.1.113730.3.3.2.177.1 ig-NG
192 collation id "" "" 1 3 2.16.840.1.113730.3.3.2.176.1 id id-ID
193 collation id NG "" 1 3 2.16.840.1.113730.3.3.2.177.1 ig-NG
}}}
I know it's ig in the old version too, but why the change from id to ig? That looks wrong to me.

Replying to [comment:4 rmeggins]:

193 collation id NG "" 1 3 2.16.840.1.113730.3.3.2.177.1 ig-NG

Thank you, Rich. This is absolutely wrong. ig-NG is Igbo - Nigeria.

A new patch is being attached.

git patch file (master) -- revised based upon the comment by Rich (Thanks!)
0001-Ticket-48936-Duplicate-collation-entries.patch

Replying to [comment:6 rmeggins]:

https://fedorahosted.org/389/attachment/ticket/48936/0001-Ticket-48936-Duplicate-collation-entries.patch has ig in it - did you post a new patch?
Yes, this patch is the latest one.

The diff for ig-NG is this pair of lines.
{{{
-collation id ID "" 1 3 2.16.840.1.113730.3.3.2.177.1 ig-NG
+collation ig "" "" 1 3 2.16.840.1.113730.3.3.2.177.1 ig ig-NG
}}}

"ig-NG" is Igbo - Nigeria, which is supposed to be in the table with the language code ig, I think.

Reviewed by Rich (Thank you!!)

Pushed to master:
6d472e4..3e3dff8 master -> master
commit 3e3dff8

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.5.12

2 years ago

Login to comment on this ticket.

Metadata