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:
Depending of the size of the groups along with the complexity of the rules and the interactions with other plugins ( typically in an IPA context ), the Auto Member rebuild task can generate performance issues ( for instance a high CPU usage when the Schema Compatibility plugin is called ). 

Therefore a customer would like to have an option to abort the rebuild task.

Version-Release number of selected component (if applicable):
RHEL 7.9

How reproducible:
Was a 1 time issue at a customer site.

Steps to Reproduce:


Actual results:
High CPU usage for several hours.

Expected results:
Allow to stop the task.

Additional info:

Upstream ticket: 

https://github.com/389ds/389-ds-base/issues/5155

Created attachment 1859850 [details]
Patch file for "RFE abort automember rebuild task" for 389-ds-base-1.3.10 branch

This patch can be used to generate a hotfix for RHEL 7.9 that adds an abort task to cancel any running "automember rebuild tasks.  This is an example on how to execute the task:

# ldapmodify -D "cn=directory manager" -W
dn: cn=my abort task, cn=automember abort rebuild,cn=tasks,cn=config
objectClass: top
objectClass: extensibleObject
cn: my abort task


In addition to the new "Abort Task" the database transaction handling was also changed around the rebuild task, and it "might" help improve the impact of the rebuild task.  It would be good to know if the abort task is still needed after applying the hotfix.

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 (Moderate: 389-ds-base security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2022:5239