Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1570033
Description of problem: After updating 389-ds-base in RHDS10 from 1.3.6.1-28 to 1.3.7.5-19, the errors log is flooded with: [13/Apr/2018:15:23:18.446577844 +0200] - WARN - keys2idl - recieved NULL idl from index_read_ext_allids, treating as empty set [13/Apr/2018:15:23:18.447111033 +0200] - WARN - keys2idl - this is probably a bug that should be reported [13/Apr/2018:15:23:18.449436104 +0200] - WARN - keys2idl - recieved NULL idl from index_read_ext_allids, treating as empty set [13/Apr/2018:15:23:18.450191611 +0200] - WARN - keys2idl - this is probably a bug that should be reported The message appears every time if the search filter is based on the attribute entrydn, and with a dn that does not exist. Version-Release number of selected component (if applicable): 389-ds-base-1.3.7.5-19.el7_5.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1570033
Metadata Update from @mreynolds: - Issue assigned to mreynolds
commit e350a26
be174a6..9f347e8 389-ds-base-1.3.8 -> 389-ds-base-1.3.8
4b823fe..7a334ca 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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: - https://github.com/389ds/389-ds-base/issues/2781
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Log in to comment on this ticket.