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.
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.
git patch file (1.2.11 only) 0001-Ticket-47731-A-tombstone-entry-is-deleted-by-ldapdel.patch
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
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1109358
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.2.11.26
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1064
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.