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.
Bug 1283915 - Caching of ipaconfig does not work in framework
Summary: Caching of ipaconfig does not work in framework
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On: 1283748
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-20 09:28 UTC by Jan Kurik
Modified: 2015-12-14 12:11 UTC (History)
11 users (show)

Fixed In Version: ipa-4.2.0-15.el7_2.1
Doc Type: Bug Fix
Doc Text:
An internal error in the method that cached ipaconfig settings caused the results not to be cached. Consequently, a search for limits stored in LDAP was unintentionally together with every LDAP search operation, and the search operations were thus duplicated. This update fixes the comparison of LDAP connections, and limits are downloaded from LDAP only once for each connection.
Clone Of: 1283748
Environment:
Last Closed: 2015-12-08 10:37:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
dirsrv_access_log (25.75 KB, text/plain)
2015-11-25 06:59 UTC, Abhijeet Kasurde
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2562 0 normal SHIPPED_LIVE ipa bug fix update 2015-12-08 15:35:22 UTC

Description Jan Kurik 2015-11-20 09:28:20 UTC
This bug has been copied from bug #1283748 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 5 Abhijeet Kasurde 2015-11-25 06:59:07 UTC
Created attachment 1098576 [details]
dirsrv_access_log

Comment 6 Abhijeet Kasurde 2015-11-25 07:05:35 UTC
Verified.

IPA server version::

ipa-server-4.2.0-15.el7_2.2.x86_64


Steps to verify ::

1. Fresh install ipa-server
2. Add IPA user 
3. tail DS access log, usually found /var/log/dirsrv/slapd-<INSTANCE>/access
4. perform operations like 'ipa user-show', 'ipa user-find' and 
5. Grep for string in DS access log
 {{
"SRCH base="cn=ipaconfig,cn=etc,dc=example.com" scope=0 filter="(objectClass=*)" attrs=ALL" 

}}

6. Note that this string should appear once for each request / connection of ipa command.

Comment 9 errata-xmlrpc 2015-12-08 10:37:27 UTC
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.

https://rhn.redhat.com/errata/RHBA-2015-2562.html


Note You need to log in before you can comment on or make changes to this bug.