Note, I was not able to reproduce the problem in the description. The resurrected entry(in 1.3.2) is correctly indexed according to dbscan. The only issue I found was that the objectclass index still contained the old tombstone key/value.

This looks good. IIRC, the problem is using index_addordel_string with flags BE_INDEX_DEL without specifying the type of index (eq, pres, etc.) to index. There are a few other places where this is done - in ldbm_delete.c, there are a few places where index_addordel_string() is called with flags BE_INDEX_DEL without specifying |BE_INDEX_EQUALITY - these need to be fixed too. Is it possible that the original problem is caused by deletion of these tombstone entries (by the replica tombstone reaper) and the index not being cleaned up properly?

revision
0001-Ticket-47323-resurrected-entry-is-not-correctly-inde.patch

Replying to [comment:6 rmeggins]:

This looks good. IIRC, the problem is using index_addordel_string with flags BE_INDEX_DEL without specifying the type of index (eq, pres, etc.) to index. There are a few other places where this is done - in ldbm_delete.c, there are a few places where index_addordel_string() is called with flags BE_INDEX_DEL without specifying |BE_INDEX_EQUALITY - these need to be fixed too. Is it possible that the original problem is caused by deletion of these tombstone entries (by the replica tombstone reaper) and the index not being cleaned up properly?

Yup, it was missing in ldap_delete.c as well. Everywhere else looked good.

New patch attached.

git merge ticket47323
Updating 4ea4c8b..95d07e1
Fast-forward
ldap/servers/slapd/back-ldbm/ldbm_add.c | 6 +++---
ldap/servers/slapd/back-ldbm/ldbm_delete.c | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)

git push origin master
4ea4c8b..95d07e1 master -> master

commit 95d07e1
Author: Mark Reynolds mreynolds@redhat.com
Date: Mon Jul 29 15:56:11 2013 -0400

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1044144

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/660

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.