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.
Cause: When deleting a node entry which descendants are all deleted, only the first position was checked.
Consequence: The child entry at the first position is usually deleted in the database, but it could be reused for the replaced tombstone entry, which reports false error "has children" and makes the node deletion fail.
Fix: Instead of checking the first position, check all the child entries and if they are tombstones or not. If all of them are tombstones, the node is deleted.
Result: The false error "has children" is no more reported and a node entry which children are all tombstones is successfully deleted.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47764
Bug description: When checking a child entry on a node, it only
checked the first position, which was normally "deleted" if there
were no more children. But in some cases, a tombstoned child was
placed there. If it occurred, even though there were no live child
any more, _entryrdn_delete_key returned "has children" and the delete
operation failed.
Created attachment 894938[details]
test ldif file
Steps to verify:
Set up 2way MMR with the suffix o=a.
Import the attached sample.ldif to a master and initialize the other master.
ldapdelete -h <host> -p <master1_port> ... << EOF
ou=child,o=x,o=a
EOF
<-- this is successful
ldapdelete -h <host> -p <master1_port> ... << EOF
o=x,o=a
EOF
This used to fail and these error messages were logged in the error log.
[..] entryrdn-index - _entryrdn_delete_key: Failed to remove o=x; has children
[..] - database index operation failed BAD 1031, err=-1 Unknown error: -1
If "o=x,o=a" is successfully deleted without any errors, the bug is verified.
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