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.
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.
On the last step search with paged results returns the blank list of entries.
Search with 'nsPagedSizeLimit = 15' and 'nsslapd-pagedsizelimit = 5', should return all 10 requested entries.
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
============================ test session starts ============================
platform linux2 -- Python 2.7.5, pytest-2.9.1, py-1.4.31, pluggy-0.3.1 -- /usr/bin/python
rootdir: /mnt/testarea/test/ds/dirsrvtests/tests/tickets, inifile:
collected 1 items
========================== 1 passed in 6.09 seconds ==========================
Marking as verified.
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
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.