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.
Bug 1109358 - A tombstone entry is deleted by ldapdelete
Summary: A tombstone entry is deleted by ldapdelete
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks: 1109360
TreeView+ depends on / blocked
 
Reported: 2014-06-13 18:13 UTC by Noriko Hosoi
Modified: 2020-09-13 20:59 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-34.el6
Doc Type: Bug Fix
Doc Text:
Cause: An failure in backend transaction post plugin was not properly passed to the backend delete. Consequence: A tombstone deletion by ldapdelete op from client was unexpectedly executed. Fix: Added a failure check code. Result: A tombstone deletion by ldapdelete op from client fails as expected.
Clone Of:
: 1109360 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:55:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1064 0 None closed A tombstone entry is deleted by ldapdelete 2020-10-08 00:06:54 UTC
Red Hat Product Errata RHBA-2014:1385 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2014-10-14 01:27:42 UTC

Description Noriko Hosoi 2014-06-13 18:13:05 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47731

{{{
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.
}}}
Comment 2 Amita Sharma 2014-07-15 10:34:31 UTC 
[root@dhcp201-155 ~]# ldapadd -x -h localhost -p 30100 -D "cn=Directory Manager" -w Secret123  << EOF
dn: ou=A,dc=example,dc=com
ou: People
ou: A   
objectClass: top
objectClass: organizationalunit
EOF                              
adding new entry "ou=A,dc=example,dc=com"

[root@dhcp201-155 ~]# ldapadd -x -h localhost -p 30100 -D "cn=Directory Manager" -w Secret123  << EOF
dn: uid=AA,ou=A,dc=example,dc=com
uid: 1456
givenName: 123
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
sn: 456
cn: 456
EOF

adding new entry "uid=AA,ou=A,dc=example,dc=com"

[root@dhcp201-155 ~]# ldapadd -x -h localhost -p 30100 -D "cn=Directory Manager" -w Secret123  << EOF
dn: uid=BB,ou=A,dc=example,dc=com
uid: 1456
givenName: 123
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
sn: 456
cn: 456
EOF

adding new entry "uid=BB,ou=A,dc=example,dc=com"


[root@dhcp201-155 ~]# ldapdelete -x -r -h localhost -p 30100 -D "cn=Directory Manager"  -w Secret123  "ou=A,dc=example,dc=com"


[root@dhcp201-155 ~]# ldapsearch -x -h localhost -p 30100 -D "cn=Directory Manager" -w Secret123 -b "dc=example,dc=com" "(objectclass=nsTombstone)" dn
# extended LDIF
#
# LDAPv3
# base <dc=example,dc=com> with scope subtree
# filter: (objectclass=nsTombstone)
# requesting: dn 
#

# ffffffff-ffffffff-ffffffff-ffffffff, example.com
dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=example,dc=com

# 028ba201-0c0611e4-bc01ffc3-e3d66826, A, example.com
dn: nsuniqueid=028ba201-0c0611e4-bc01ffc3-e3d66826,ou=A,dc=example,dc=com

# 264ee801-0c0611e4-bc01ffc3-e3d66826, AA, A, example.com
dn: nsuniqueid=264ee801-0c0611e4-bc01ffc3-e3d66826,uid=AA,ou=A,dc=example,dc=c
 om

# 264ee802-0c0611e4-bc01ffc3-e3d66826, BB, A, example.com
dn: nsuniqueid=264ee802-0c0611e4-bc01ffc3-e3d66826,uid=BB,ou=A,dc=example,dc=c
 om

# search result
search: 2
result: 0 Success

# numResponses: 5

[root@dhcp201-155 ~]# ldapdelete -x -r -h localhost -p 30100 -D "cn=Directory Manager"  -w Secret123  "ou=A,dc=example,dc=com"
ldap_search: No such object (32)
ldap_delete: No such object (32)
	matched DN: dc=example,dc=com
[root@dhcp201-155 ~]# ldapdelete -x -r -h localhost -p 30102 -D "cn=Directory Manager"  -w Secret123  "ou=A,dc=example,dc=com"
ldap_search: No such object (32)
ldap_delete: No such object (32)
	matched DN: dc=example,dc=com
[root@dhcp201-155 ~]# ldapdelete -x -r -h localhost -p 30102 -D "cn=Directory Manager"  -w Secret123  "uid=BB,ou=A,dc=example,dc=com"
ldap_search: No such object (32)
ldap_delete: No such object (32)
	matched DN: dc=example,dc=com
[root@dhcp201-155 ~]# ldapdelete -x -r -h localhost -p 30102 -D "cn=Directory Manager"  -w Secret123  "uid=AA,ou=A,dc=example,dc=com"
ldap_search: No such object (32)
ldap_delete: No such object (32)
	matched DN: dc=example,dc=com
[root@dhcp201-155 ~]# ldapdelete -x -r -h localhost -p 30100 -D "cn=Directory Manager"  -w Secret123  "uid=AA,ou=A,dc=example,dc=com"
ldap_search: No such object (32)
ldap_delete: No such object (32)
	matched DN: dc=example,dc=com

Hence VERIFIED.
Comment 3 errata-xmlrpc 2014-10-14 07:55:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1385.html
Note You need to log in before you can comment on or make changes to this bug.