https://bugzilla.redhat.com/show_bug.cgi?id=624442
https://bugzilla.redhat.com/attachment.cgi?id=473440&action=diff
https://bugzilla.redhat.com/attachment.cgi?id=473440&action=edit
Description: Each replica has an RUV tombstone entry in the
backend db, which keeps nsds50ruv attribute values as follows:
nsds50ruv: {replicageneration}<replica_generation_csn>
nsds50ruv: {replica<rid> ldap://<host>:<port>}<last_modified>
...
When the replica is deleted, the RUV tombstone entry remains
in the db. Then if the replica is added back with the different
replica id<rid-2>, the original nsds50ruv value {replica<rid>
ldap://<host>:<port>} was not updated. This caused the problem
if the counter replica server happened to get the same replica
id<rid> that this server original had.
This patch compares the replica id<rid> in the RUV tombstone
entry with the new id<rid-2>. If they don't match, recreate
the RUV tombstone entry.