If a request is sent to server using paged searches and the suffix has a subsuffix, the results corresponding to the subsuffix are not shown in the query when the number of records per page is less than cardinal of the main suffix.
Hope it will be clear in the steps to reproduce:
import a few entries as in attachment (see redhat.ldif and subsuffix.ldif).
ldapsearch the entire suffix with root entry as base dn and subtree scope. You will see all the entries.
Now use option "-E pr=<entries per page>/noprompt.
if <entries per page> is less than number of records in main suffix, the subsuffix entries will not appear in the request result.
if <entries per page> is greater or equal than number of records in the main suffix, we should see all the entries as requested.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1117975
git patch file (master)
Looks good. For the CI test, even if we are not using the tmp directory we should still clear it, because someone might copy/paste the script for a new testcase and that new testcase might use the tmp directory:
# clear the tmp directory
git patch file (master) -- revised following the advice from Mark.
Reviewed by Mark (Thank you!!)
Pushed to master:
eb5fde9..b116d7e master -> master
Ticket #47824 - paged results control is not working in some cases when we have a subsuffix.
b116d7e..8b305c1 master -> master
Ticket 47824 - CI test: add test case for ticket 47824
Changing the target milestone to 1.2.11.
Pushed to 389-ds-base-1.3.2:
7c5d8f2..0bc9016 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
Pushed to 389-ds-base-1.2.11:
c6ad00b..9674195 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
Pushed to master:
bff1dd4..e3a7705 master -> master
Author: Simon Pichugin email@example.com
Date: Wed Jul 20 10:10:55 2016 +0200
Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 188.8.131.52
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
to comment on this ticket.