This bug is created as a clone of upstream ticket:
Report by Rich:
I have a situation where I have added several entries under ou=people, then deleted all of those entries and ou=people. When I reindex entryrdn, I do not see all of the tombstone entries in entryrdn, plus I see the following errors:
[30/Jan/2012:20:06:07 -0700] entryrdn-index - _entryrdn_insert_key: Getting "nsuniqueid=ca681083-69f011e0-8115a0d5-f42e0a24,ou=People,dc=vmhost,dc=com" failed: Successful return: 0(0)
See upstream ticket for steps to verify
# Reindexing entryrdn fils if ancestors are also tombstoned.
Technical note added. If any revisions are required, please edit the
"Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content
Cause: In case a non-leaf entry is tombstoned, the RDN starts with nsuniqueid. The special RDN in non-leaf entries was not supported.
Consequence: Inserting/traversing the entryrdn index fails if a parent
entry is tombstoned.
Fix: The special RDN of the non-leaf tombstone entry is supported.
Result: Inserting/traversing the entryrdn index works even if tombstone entries are found among non-leaf entries.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: Reindexing (e.g. using db2index) the entryrdn index when there are deleted entries that were converted to tombstone entries in the database.
Consequence: Error messages like _entryrdn_insert_key: Getting "nsuniqueid=ca681083-69f011e0-8115a0d5-f42e0a24,ou=People,dc=example,dc=com" failed are seen.
Fix: The server correctly handles these child tombstone entries.
Result: The entryrdn index can be reindexed with no errors and searches work correctly.
mmrepl mmraccept startup 100% (2/2)
mmrepl mmraccept run 100% (23/23)
mmrepl mmraccept cleanup 100% (1/1)
Hence marking bug 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.