Bug 2219000

Summary: subsuffix are not returned in one level scoped search
Product: Red Hat Directory Server Reporter: mreynolds
Component: 389-ds-baseAssignee: Pierre Rogier <progier>
Status: CLOSED MIGRATED QA Contact: LDAP QA Team <idm-ds-qe-bugs>
Severity: high Docs Contact: Evgenia Martynyuk <emartyny>
Priority: urgent    
Version: 11.8CC: eperuch, idm-ds-dev-bugs, lofanni, msugaya, musoni, progier, tbordaz, tmihinto, tscherf, vashirov
Target Milestone: DS12.5Keywords: Triaged
Target Release: dirsrv-12.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sync-to-jira
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2292903 (view as bug list) Environment:
Last Closed: 2024-06-26 13:53:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2292903    
Attachments:
Description Flags
Case 03838109 none

Description mreynolds 2023-06-30 21:31:06 UTC
Description of problem:

subsuffix are not returned in one level scoped search

Steps to reproduce the behavior:

- Create an instance with dc=example,dc=com suffix (with entries in the backends)
- Create a subsuffix just below the suffix with entries:
- dsconf instance backend create --suffix ou=foo,dc=example,dc=com --create-entries --be-name foo
- Run ldapsearch ldapsearch with sub scope:

    ldapsearch -Q -LLL -Y EXTERNAL -H ldapi://%2fvar%2frun%2fslapd-i1.socket -s sub -b dc=example,dc=com '(ou=*)' dn
    (No errors: ou=foo,dc=example,dc=com is listed)

- Run ldapsearch with one scope:

    ldapsearch -Q -LLL -Y EXTERNAL -H ldapi://%2fvar%2frun%2fslapd-i1.socket -s one -b dc=example,dc=com '(ou=*)' dn
    (Error: ou=foo,dc=example,dc=com is not listed)

Expected results

    ou=foo,dc=example,dc=com should be listed in both cases

Additional context

    This behavior confuses some ldap browsers that cannot show any more the entries below sub suffix.

Upstream ticket:

    https://github.com/389ds/389-ds-base/issues/5772

Comment 1 eperuch 2024-06-06 16:26:25 UTC
Created attachment 2036610 [details]
Case 03838109

This bug is critical for the customer, blocking them to upgrade from an unsupported version for which they are paying, RHDS 10.0.0 to 12.5

Comment 4 Lorenzo Fanni 2024-06-26 09:33:55 UTC
Hi all,
today I just did a fresh install of RHEL 9.4 and installed RHDS 12.4.
I created a suffix (dc=fanni,dc=test) and a sub-suffix (ou=prova,dc=fanni,dc=test) but the behavior seems the same.
I attach a text file with the result of the query with scope "one": I still can't see the sub-suffix.

Comment 5 Lorenzo Fanni 2024-06-26 09:45:34 UTC
(In reply to Lorenzo Fanni from comment #4)
> Hi all,
> today I just did a fresh install of RHEL 9.4 and installed RHDS 12.4.
> I created a suffix (dc=fanni,dc=test) and a sub-suffix
> (ou=prova,dc=fanni,dc=test) but the behavior seems the same.
> I attach a text file with the result of the query with scope "one": I still
> can't see the sub-suffix.

We need the product will work with the previous query option "-s one" like in the 10 RHDS version

Comment 7 Viktor Ashirov 2024-06-26 13:53:29 UTC
This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-56. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.