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.
DescriptionKaushik Banerjee
2013-01-23 10:29:44 UTC
Description of problem:
Group lookup hangs for a minute if member dn is incorrect.
Version-Release number of selected component (if applicable):
1.9.2-74
How reproducible:
Always
Steps to Reproduce:
1. Add a group as follows:
dn: cn=Group_02,ou=Groups,dc=example,dc=com
gidNumber: 10120
objectClass: top
objectClass: groupOfNames
objectClass: posixGroup
cn: Group_02
member: uid=kuser1 <== I removed ",dc=example,dc=com"
2. Try to lookup the group
# time getent group Group_02
real 0m58.008s <== Takes almost a minute to return back to shell
user 0m0.000s
sys 0m0.001s
3.
Actual results:
Group lookup fails and takes a minute to come back to shell.
Expected results:
Group lookup shouldn't fail, but shouldn't return any members either.
Additional info: