Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
This issue is similar to this bug fixed some time ago:
https://fedorahosted.org/389/ticket/48223
for winsync.
In this case DN normalization at import time is considering that, for instance,
these two dn's are duplicated:
================================
dn: cn=user nuevo,ou=people,o=redhat
objectclass: inetorgperson
cn: user nuevo
sn: usernuevo
userpassword: user49
dn: cn=user nuevo,ou=people,o=redhat
objectclass: inetorgperson
cn: user nuevo
sn: us
userpassword: user49
================================
errors:
[04/Jan/2017:15:02:50.356169698 +0100] entryrdn-index - _entryrdn_insert_key: Same DN (dn: cn=user nuevo,ou=people,o=redhat) is already in the entryrdn file with different ID 53. Expected ID is 54.
[04/Jan/2017:15:02:50.399342349 +0100] import userRoot: Duplicated DN detected: "cn=user nuevo,ou=people,o=redhat": Entry ID: (54)
To reproduce, just import both entries in the same ldif file.
not sure if this is, in fact a feature (it does not seem to me from rfc4514) or if fixing this could break something else.
If this is not corresponding or too risky, let's close this.
Thanks.
German.