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 1665752 - Bug 1598186 is still reproducible with 389-ds-base-1.3.8.4-18.
Summary: Bug 1598186 is still reproducible with 389-ds-base-1.3.8.4-18.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.6
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: 7.7
Assignee: mreynolds
QA Contact: RHDS QE
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-13 18:25 UTC by Têko Mihinto
Modified: 2020-09-13 22:18 UTC (History)
11 users (show)

Fixed In Version: 389-ds-base-1.3.9.1-2.el7
Doc Type: Bug Fix
Doc Text:
.Searches with scope `one` no longer return incomplete results in Directory Server Previously, when a user performed a search with a scope set to `one`, the search operation did not return all expected entries. With this update, Directory Server correctly creates the entry candidates list for one level searches. As a result, the server returns the expected entries.
Clone Of:
Environment:
Last Closed: 2019-08-06 12:59:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 3293 0 None closed one level search returns not matching entry 2021-02-01 13:18:44 UTC
Red Hat Product Errata RHBA-2019:2152 0 None None None 2019-08-06 12:59:32 UTC

Description Têko Mihinto 2019-01-13 18:25:00 UTC
Description of problem:

Bug 1598186 is still reproducible with 389-ds-base-1.3.8.4-18.


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

# rpm -qa | grep 389-ds-base
389-ds-base-1.3.8.4-18.el7_6.x86_64
389-ds-base-libs-1.3.8.4-18.el7_6.x86_64
#

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.5 (Maipo)
#


How reproducible:

Always with the customer configuration ( nsslapd-idlistscanlimit: 170000 ).


Steps to Reproduce:

1. Install 389-ds-base-1.3.7.5-25
2. Create a new RHDS instance
3. Set the "nsslapd-idlistscanlimit" to a high value ( for instance 170000 )
4. Import the LDIF data
5. Run the search with scope=one.
It returns an entry that doesn't match the filter.
6. Upgrade to 389-ds-base-1.3.8.4-18
7. Redo steps 2, 3, 4 and 5.
The search returns again a non-matching entry while bug 1598186 is expected
to be included in the 389-ds packages since version 1.3.8.4-4


Actual results:

Bug 1598186 is still reproducible.


Expected results:

Bug 1598186 should be fixed.


Additional info:

Comment 26 errata-xmlrpc 2019-08-06 12:59:10 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://access.redhat.com/errata/RHBA-2019:2152


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