[389-devel] Re: Please review (additional fixes): [389 Project] #48755: moving an entry could make the online init fail

On 06/20/2016 02:20 AM, Ludwig Krispenz wrote:

I have a question about your tombstone entry...  You are using entrydn instead of entryrdn?

no, sorry for the confusion, I was using ldapsearch to get teh tombstones, not dbscan

Hmmm, if that's the case, I need to learn why you don't have the parent-child relationship in your parentid index...  As I copied&pasted, tombstone entry should be in the index... :(

> dn: nsuniqueid=bd76ad01-322c11e6-a5389989-c3cc84f8,cn=x,ou=People,dc=example,dc=com
> entryid: 30
> parentid: 2

Is that the default configuration for IPA?  Does that mean IPA has no move issue?

  27 ldbm_back_delete( Slapi_PBlock *pb )
 781         if(create_tombstone_entry)
 903             if (entryrdn_get_switch()) /* subtree-rename: on */
 907                 /* To maintain tombstonenumsubordinates,
 908                  * parentid is needed for tombstone, as well. */
 913                     retval = index_addordel_values_sv(be, LDBM_PARENTID_STR,
 914                                                       svals, NULL, e->ep_id,
 915                                                       BE_INDEX_ADD, &txn);

But in that case total update is supposed to have no change...

313 repl5_tot_run(Private_Repl_Protocol *prp)
441     if (is_entryrdn) {
                // NEW BULK IMPORT
493     } else {
494         /* Original total update */
    [...]
525     }