#49971 Ticket 49968 - Confusing CRITICAL message: list_candidates - NULL idl was recieved from filter_candidates_ext
Closed by spichugi. Opened by tbordaz.
tbordaz/389-ds-base ticket_49968  into  master

Download 49971.patch

Bug Description:
When a filter component is indexed but returns an empty IDL
an alarming message is logged although it is normal.

Fix Description:
Remove the alarming message

https://pagure.io/389-ds-base/issue/49968

Reviewed by: ?

Platforms tested: F27 + testcase

Flag Day: no

Doc impact: no

rebased onto bba53215a8fcf7e77f781c0f02c4512fce3c8b04

rebased onto bba53215a8fcf7e77f781c0f02c4512fce3c8b04

@tbordaz - was this already merged?

@mreynolds - yes it was. There was a pagure bug ('merge' button not working) so I pushed the fix the old way.
I am not sure what to do with this PR that is now useless

Pull-Request has been closed by mreynolds

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3030

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

Metadata