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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47750

Example:
dn: ou=test,ou=projects,nsuniqueid=bd44c40a-afc711e3-9b7bd5e4-7027b69c
 +o=org246,ou=ou0,dc=example,dc=com

Trying to resurrect ou=test and adding a glue entry ou=projects.  Then, the add fails due to its parent not found since o=org246 is a conflict.

210 create_glue_entry ( Slapi_PBlock *pb, char *sessionid, Slapi_DN *dn, const char *uniqueid, CSN *opcsn )
239             op_result= do_create_glue_entry(rdn, superiordn, uniqueid, "missingEntry", opcsn);
254                 case LDAP_NO_SUCH_OBJECT:
255                     /* The parent is missing */
256                     {
257                     /* JCMREPL - Create the parent ... recursion?... but what's the uniqueid? */
258                     PR_ASSERT(0); /* JCMREPL */ <== This assertion fails.
259                     }

Steps to reproduce: https://bugzilla.redhat.com/show_bug.cgi?id=1080185#c1

Without this fix, DS returns a wrong entry.  This is a data inconsystency bug.

Fixed by Mark in upstream:
https://fedorahosted.org/389/attachment/ticket/47750/0001-Ticket-47750-During-delete-operation-do-not-refresh-.patch

$ rpm -qa | grep 389
389-ds-base-libs-1.3.3.1-11.el7.x86_64
389-ds-base-1.3.3.1-11.el7.x86_64

After running reproducer, in the logs:
./slapd-M1/errors:[15/Jan/2015:21:38:29 +0100] NSMMReplicationPlugin - conn=2254 op=119 csn=54b82545000004d00000: Can't resurrect tombstone to glue reason 'deletedEntryHasChildren'. Try with conflict dn o=bees3,ou=organizations,dc=example,dc=com, error=68
./slapd-M3/errors:[15/Jan/2015:21:38:29 +0100] NSMMReplicationPlugin - conn=2216 op=132 csn=54b82545000004d00000: Can't resurrect tombstone to glue reason 'deletedEntryHasChildren'. Try with conflict dn o=bees3,ou=organizations,dc=example,dc=com, error=68


Marking as VERIFIED.

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/RHSA-2015-0416.html