A tombstone entry is deleted by ldapdelete

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47731

• Created at 2014-03-07 03:22:50 by nhosoi (@nhosoi)
• Closed as Fixed
• Assigned to nhosoi (@nhosoi)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1109360
  • https://bugzilla.redhat.com/show_bug.cgi?id=1109358

---

Steps:
1. add entries
ou=People,dc=example,dc=com
uid=A,ou=People,dc=example,dc=com
uid=B,ou=People,dc=example,dc=com

2. delete entries 
uid=A,ou=People,dc=example,dc=com
uid=B,ou=People,dc=example,dc=com
ou=People,dc=example,dc=com

3. search tombstone entries
ldapsearch [...] -b 'dc=example,dc=com' "(objectclass=nstombstone)" dn
dn: nsuniqueid=...,ou=People,dc=example,dc=com
dn: nsuniqueid=...,uid=A,ou=People,dc=example,dc=com
dn: nsuniqueid=...,uid=B,ou=People,dc=example,dc=com

4. delete "uid=A"; it's successfully deleted, which should not be.
5. delete "ou=People"; it's successfully deleted. 
   1) a tombstone entry should not be deleted any way. 
   2) even if a child tombstone entry uid=B exists, ou=People is deleted.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2014-03-07 03:33:12

Description: A tombstone deletion by ldapdelete op from client is
supposed to fail. The failure from SLAPI_PLUGIN_BETXNPOSTOPERATION
was ignored in 389-ds-base-1.2.11 plugin_call_func and it was not
passed to the backend to abort. This patch added the check in the
same way as in 389-ds-base-1.3.1 and newer.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2014-03-07 03:33:53

git patch file (1.2.11 only)
0001-Ticket-47731-A-tombstone-entry-is-deleted-by-ldapdel.patch

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2014-03-08 03:50:23

Reviewed by Rich (Thank you!!)

Pushed to 389-ds-base-1.2.11:
e0fd1ff..e1f92c0 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit cca1fb5

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2014-06-14 00:13:07

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

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 23:05:34

Metadata Update from @nhosoi:

• Issue assigned to nhosoi
• Issue set to the milestone: 1.2.11.26