An attempt to delete a tombstone entry gives err=32 - no such entry:
17/May/2012:01:41:35 +0000] conn=947 fd=80 slot=80 SSL connection from ::1 to ::1 [17/May/2012:01:41:35 +0000] conn=947 SSL 256-bit AES [17/May/2012:01:41:35 +0000] conn=947 op=0 BIND dn="cn=Directory Manager" method=128 version=3 [17/May/2012:01:41:35 +0000] conn=947 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager" [17/May/2012:01:41:35 +0000] conn=947 op=1 DEL dn="nsuniqueid=14403301-1dd211b2-9635fc8a-5f520000,uid=username,ou=people,dc=example,dc=com" [17/May/2012:01:41:35 +0000] conn=947 op=1 RESULT err=32 tag=107 nentries=0 etime=0 [17/May/2012:01:41:35 +0000] conn=947 op=1 RESULT err=32 tag=107 nentries=0 etime=0 [17/May/2012:01:41:35 +0000] conn=947 op=2 UNBIND [17/May/2012:01:41:35 +0000] conn=947 op=2 fd=80 closed - U1
Note there are two result lines - this is bad.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=830342
set default ticket origin to Community
Added initial screened field value.
Manual tombstone deletion is not recommended/supported. . As described in comment 6, the operation is only allowed when the tombstone entry is in entry cache. . Even if a tombstone entry is deleted on a master, the operation is not replicated to the consumers. . The same symptom is observed on RHDS8.2, as well. . We strongly recommend to use tombstone reap to clean up tombstone entries. A doc bug was filed for that: Bug 974695 - Adding tombstone entry and how to delete it to Admin Guide.
Metadata Update from @nkinder: - Issue assigned to mreynolds - Issue set to the milestone: N/A
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/376
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: Invalid)
Login to comment on this ticket.