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.

Description of problem:
In some cases, it is not possible to delete an entry which had conflicts in its children. 

According to the Ludwig comment: https://bugzilla.redhat.com/show_bug.cgi?id=1539082#c8
"There is still an issue with numsubordinate count in the more complex scenarios, it always remains numsubordinates: 1 although it should be 0. But in the test case it oscillates between 1 and 40."

Version-Release number of selected component (if applicable):
389-ds-base-1.3.7.5-18.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run the test case
$ py.test -s -v dirsrvtests/tests/suites/replication/conflict_resolve_test.py::Te
stTwoMasters::test_complex_add_modify_modrdn_delete

It will fail on the tear down when it tries to delete the container entry.

Actual results:
The operation gives 'Operation not allowed on non-leaf'

Expected results:
Container entry should be deleted

Upstream ticket:
https://pagure.io/389-ds-base/issue/49591

AS discussed by the team, closing this bug as wont fix.