This bug is created as a clone of upstream ticket:
setup replication with 1.2.10.a6 or earlier - verify replication is working
upgrade to 1.2.10.a8
do a search like this:
ldapsearch -xLLL -D "cn=directory manager" -w password -b dc=example,dc=com '(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectclass=nstombstone))'
You will see no entries returned. The entryrdn.db4 looks like this:
ID: 1; RDN: "dc=example,dc=com"; NRDN: "dc=example,dc=com"
ID: 10; RDN: "nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff"; NRDN: "nsunique
That is, it thinks the ruv tombstone rdn is a suffix instead of a child of dc=example,dc=com
Steps to reproduce with RHDS needed.
Adding a test case to tet.
It's already there (in mmrepl/accept.sh bug788729 :p).
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: Attempt to search for the RUV tombstone entry (as is done by client such as repl-monitor).
Consequence: The entry is not found.
Fix: Correctly index this entry in the entryrdn index.
Result: Searches for RUV tombstone entries work correctly.
mmrepl mmraccept startup 100% (2/2)
mmrepl mmraccept run 100% (23/23)
mmrepl mmraccept cleanup 100% (1/1)
Hence 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.