Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1598186 - A search with the scope "one" returns a non-matching entry.
A search with the scope "one" returns a non-matching entry.
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
7.5
All Linux
high Severity high
: rc
: ---
Assigned To: mreynolds
RHDS QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-04 10:46 EDT by Têko Mihinto
Modified: 2018-10-30 06:15 EDT (History)
5 users (show)

See Also:
Fixed In Version: 389-ds-base-1.3.8.4-4.el7
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-30 06:14:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3127 None None None 2018-10-30 06:15 EDT

  None (edit)
Description Têko Mihinto 2018-07-04 10:46:15 EDT
Description of problem:

An ldapsearch command is returning an entry that does not match the search filter.
This happens only when the one scope is specified.
Subtree scope works fine.


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


# rpm -qa | grep 389-ds-base-1
389-ds-base-1.3.7.5-21.el7_5.x86_64
#

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


How reproducible:

With the customer configuration, always.

Steps to Reproduce:

1. Setup the configuration
2. Import LDIF data
3. Run the search with scope=one.
It returns an entry that doesn't match the filter.


Actual results:
The search return a wrong entry.

Expected results:
Only matching entries should be returned.


Additional info:
Comment 15 errata-xmlrpc 2018-10-30 06:14:34 EDT
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/RHSA-2018:3127

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