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 1258996 - Some filters in RHDS10 are not working fine.
Summary: Some filters in RHDS10 are not working fine.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 1133060 1259999
TreeView+ depends on / blocked
 
Reported: 2015-09-01 17:12 UTC by German Parente
Modified: 2020-09-13 21:30 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.3.4.0-15.el7
Doc Type: Bug Fix
Doc Text:
Complex filters in a search request did not work as expected. Now, the filter optimization no longer mistakenly ignores certain complex subfilters.
Clone Of:
: 1259999 (view as bug list)
Environment:
Last Closed: 2015-11-19 11:44:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1596 0 None None None 2020-09-13 21:30:53 UTC
Red Hat Product Errata RHBA-2015:2351 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2015-11-19 10:28:44 UTC

Description German Parente 2015-09-01 17:12:20 UTC 
Description of problem:

export to ldif in RHDS9, re-import in RHDS10, fresh installs. Certain queries are not working as expected. Seems as if RHDS10 is ignoring some clauses of the filter.

Version-Release number of selected component (if applicable): 389-ds-base-1.3.3.1-20

How reproducible: always

Steps to Reproduce:

1. schemacheck: off + syntaxcheck: off 

2. Import this ldif file in both rhds9 and rhds10 instances:

-----------------------------------
dn: o=redhat
objectClass: top
objectClass: organization
o: redhat

dn: ou=People,o=redhat
objectClass: top
objectClass: organizationalunit
ou: people

dn: uid=german.parente,ou=People,o=redhat
objectClass: organizationalPerson
objectClass: inetorgperson
objectClass: person
objectClass: top
ou: test
manager: test.manager
uid: german.parente
sn: parente
c: SE
givenName: german
o: redhat.com
l: EU
cn: German Parente

dn: uid=test.user,ou=People,o=redhat
givenName: Tester
objectClass: top
objectClass: inetorgperson
objectClass: organizationalPerson
objectClass: person
ou: test
mail: test
uid: test.user
cn: Test User
manager: test
o: redhat.com
l: EU
description: Login user
sn: Test user
c: SE
-----------------------------------

3. Do this query: 

ldapsearch -xLLL -p 2389 -h localhost -D "cn=directory manager" -w secret12 -b "o=redhat" '(&(objectclass=person)(&(|(l=EU)(l=AP)(l=NA))(|(C=SE)(c=DE)))(|(uid=*test*)(cn=*test*))(!(telephone=*)))' dn


Actual results:

in RHDS9 => 
dn: uid=test.user,ou=People,o=redhat

in RHDS10 => 
dn: uid=german.parente,ou=People,o=redhat
dn: uid=test.user,ou=People,o=redhat

Expected results:

only "dn: uid=test.user,ou=People,o=redhat"

Because the clause 

(|(uid=*test*)(cn=*test*))

that is one of the four &'s is false for "uid=german.parente".

Additional info:

If I remove, in RHDS10 the 4th clause of the &, that is to say, "(!(telephone=*))" the results are fine.

Sorry that I have not been able to debug this more deeply.
Comment 2 Noriko Hosoi 2015-09-01 18:05:49 UTC 
Thank you, German.  I could reproduce the problem.  Very odd...  Investigating...
Comment 3 Noriko Hosoi 2015-09-01 21:46:44 UTC 
Upstream ticket:
https://fedorahosted.org/389/ticket/48265
Comment 10 Amita Sharma 2015-09-08 07:21:19 UTC 
[root@dhcp201-167 export]# ldapadd -x -h localhost -p 389 -D "cn=directory manager" -w Secret123 -f /export/sample.ldif
adding new entry "o=redhat"

adding new entry "ou=People,o=redhat"

adding new entry "uid=german.parente,ou=People,o=redhat"

adding new entry "uid=test.user,ou=People,o=redhat"

[root@dhcp201-167 export]# ldapsearch -xLLL -p 389 -h localhost -D "cn=Directory Manager" -w Secret123 -b "o=redhat" '(&(objectclass=person)(&(|(l=EU)(l=AP)(l=NA))(|(C=SE)(c=DE)))(|(uid=*test*)(cn=*test*))(!(telephone=*)))' dn
dn: uid=test.user,ou=People,o=redhat

[root@dhcp201-167 export]# rpm -qa | grep 389
389-ds-base-devel-1.3.4.0-15.el7.x86_64
389-ds-base-libs-1.3.4.0-15.el7.x86_64
389-ds-base-1.3.4.0-15.el7.x86_64
389-ds-base-debuginfo-1.3.4.0-15.el7.x86_64

Hence VERIFIED.
Comment 11 errata-xmlrpc 2015-11-19 11:44:11 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-2351.html
Note You need to log in before you can comment on or make changes to this bug.