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.
Description of problem:
Potential deadlocks can occur when tasks are added to the Directory Server. Where the task itself creates new thread and makes database updates, and the task add operation also triggers post plugins to fire off.
Version-Release number of selected component (if applicable):
How reproducible:
Sometimes
Steps to Reproduce:
1. Install FreeIPA server:
# ipa-server-install
2. Authenticate as admin:
# kinit admin
3. Add a hostgroup:
# ipa hostgroup-add --desc="Web Servers" webservers
4. Add a host:
# ipa host-add web1.example.com --force
5. Add an automember rule:
# ipa automember-add --type=hostgroup webservers
# ipa automember-add-condition --key=fqdn --type=hostgroup --inclusive-regex=^web[1-9]+\.example\.com webservers
6. Try to rebuild membership:
# cat rebuild.ldif
dn: cn=rt,cn=automember rebuild membership,cn=tasks,cn=config
changetype: add
objectClass: top
objectClass: extensibleObject
cn: rt
basedn: cn=computers,cn=accounts,dc=idm,dc=lab,dc=eng,dc=brq,dc=redhat,dc=com
filter: (fqdn=*)
scope: sub
7. ldapmodify -x -D 'cn=directory manager' -w password -f rebuild.ldif
adding new entry "cn=rt,cn=automember rebuild membership,cn=tasks,cn=config"
Actual results:
The ldapmodify in step 7 hangs
Expected results:
ldapmodify does not hang the Directory Server
Moving to the right component. But I still think that this is not an issue for RHEL-6.5. If this is the case, I would kindly ask reporter or asignee to close it.
Given that the backtraces showed that this was an interaction between slapi-nis's internal locking and the transaction locks which we're using in later releases, we're now confident that this bug doesn't affect 6.x releases. Marking as closed->next release, because we're fixing it there.