Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1200826[details]
Reproducer written in Python and pytest
Description of problem:
According to the info provided by Ludwig and the information from the documentation (Administration Guide - 11.12. MANAGING DELETED ENTRIES WITH REPLICATION), it should not be possible to delete a tombstone entry from a client connection. Even binding as Directory Manager.
Now it is possible.
Version-Release number of selected component (if applicable):
389-ds-base-1.3.5.10-10.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install an instance of RHDS
2. Enable USN plugin
3. Restart the server
4. Add a user
5. Delete the user
6. Find out the tombstone entry DN for the user:
ldapsearch -D "cn=directory manager" -w Secret123 -b "dc=example,dc=com" "(&(objectClass=nstombstone)(cn=testuser))"
7. Try to delete this entry while binding as Directory Manager
Actual results:
It shouldn't be possible
Expected results:
It is possible to delete the tombstone entry
Additional info:
I've written a Python reproducer. Please, find it in the attachment.
This bug was logged because of unclear communication from DEV to QE.
when the patch was implemented to allow the deletion of a tombstone in 7.3 to be compatible to 6.x I said that the behaviour is incorrect, but we should not remove the possibility to directly remove tombstones by external operations. AN admin might want/have to do this.
Will close as not a bug
Created attachment 1200826 [details] Reproducer written in Python and pytest Description of problem: According to the info provided by Ludwig and the information from the documentation (Administration Guide - 11.12. MANAGING DELETED ENTRIES WITH REPLICATION), it should not be possible to delete a tombstone entry from a client connection. Even binding as Directory Manager. Now it is possible. Version-Release number of selected component (if applicable): 389-ds-base-1.3.5.10-10.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Install an instance of RHDS 2. Enable USN plugin 3. Restart the server 4. Add a user 5. Delete the user 6. Find out the tombstone entry DN for the user: ldapsearch -D "cn=directory manager" -w Secret123 -b "dc=example,dc=com" "(&(objectClass=nstombstone)(cn=testuser))" 7. Try to delete this entry while binding as Directory Manager Actual results: It shouldn't be possible Expected results: It is possible to delete the tombstone entry Additional info: I've written a Python reproducer. Please, find it in the attachment.