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 1331343 - Paged results search returns the blank list of entries
Summary: Paged results search returns the blank list of entries
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
Petr Bokoc
Depends On:
Blocks: 1335107
TreeView+ depends on / blocked
Reported: 2016-04-28 10:41 UTC by Simon Pichugin
Modified: 2020-09-13 21:43 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Simple paged results searches no longer return `0` instead of the actual results Previously, when a simple paged results slot in a connection was discarded due to an error such as `SIZELIMIT_EXCEEDED`, the discarded slot was not cleaned up properly. Subsequent searches which reused this slot then always returned `0`. With this update, discarded simple paged results slots are cleaned up correctly, and searches return correct results even with reused slots.
Clone Of:
: 1335107 (view as bug list)
Last Closed: 2016-11-03 20:41:32 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1868 0 None None None 2020-09-13 21:43:07 UTC
Red Hat Product Errata RHSA-2016:2594 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2016-11-03 12:11:08 UTC

Description Simon Pichugin 2016-04-28 10:41:41 UTC
Description of problem:
After series of actions, paged result search that should returns list of entries returns blank list of entries. It is hardly reproducible manually, but it is easy to reproduce with python automation.

Version-Release number:

How reproducible:

Step to reproduce: 
1. Create DS standalone instance
2. Create user for search operations
Run test for checking support of multiple paging controls on a single connection - Trac 260
3. Run test for abandon search request with setting page_size = 0
4. Run test for 'nsPagedSizeLimit = 5' and 'nsslapd-pagedsizelimit = 15', its override feature. Search with page size 10 - expect to fail.
5. Run test for 'nsPagedSizeLimit = 15' and 'nsslapd-pagedsizelimit = 5', its override feature. Search with page size 10 - expect to pass.

Actual results: 
On the last step search with paged results returns the blank list of entries. 

Expected results:
Search with 'nsPagedSizeLimit = 15' and 'nsslapd-pagedsizelimit = 5', should return all 10 requested entries.

Additional information: 
When I try to do it manually - everything is okay.
When I try to move last test case to another place (for example at the beginning), it is PASSed.
When I remove only "Test support multiple paging controls on a single connection" - last and other tests PASS
When I remove only "Abandon search request with setting page_size = 0" - last and other tests PASS
Also if switch the order of last two test cases, everything will PASS.

I do tear down with deleting users and setting attributes to the default values after each test case.

Upstream ticket - https://fedorahosted.org/389/ticket/48808

Comment 3 Simon Pichugin 2016-05-05 09:41:32 UTC
Build tested:

============================ test session starts ============================
platform linux2 -- Python 2.7.5, pytest-2.9.1, py-1.4.31, pluggy-0.3.1 -- /usr/bin/python
cachedir: dirsrvtests/tests/tickets/.cache
rootdir: /mnt/testarea/test/ds/dirsrvtests/tests/tickets, inifile:
plugins: cov-2.2.1
collected 1 items

dirsrvtests/tests/tickets/ticket48808_test.py::test_ticket48808 PASSED

========================== 1 passed in 6.09 seconds ==========================

Marking as verified.

Comment 4 Simon Pichugin 2016-05-06 10:38:01 UTC
Verification process was automated at repo - https://git.fedorahosted.org/cgit/389/ds.git/

Test case file is located at dirsrvtests/tests/tickets/ticket48808_test.py

Comment 10 errata-xmlrpc 2016-11-03 20:41:32 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.


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