This is an extension of #1322, where we implement a quick fix for the stable 1.8 branch.
We can handle the errors from LDAP even better, though. We could introduce a new option that would control whether we want to abort the operation completely or try to carry on.
We should also make sure that when errors are ignored, we don't treat the result as "entry not found" and delete cached entries.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11.0 (LTM) summary: Handle LDAP errors better => Need option to be strict or non strict with size limit errors on paging
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=820631
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=820631 820631]
proposed_priority: => Optional
This ticket has been evaluated for inclusion into SSSD 1.10 release and was decided to be excluded since it does not match the main goals and themes of the release. It might be considered for later releases.
milestone: SSSD 1.11.0 (LTM) => SSSD 1.12
The downstream ticket was closed and I would like to close this ticket as well. Moving to triage for proper discussion with other developers.
changelog: => design: => design_review: => 0 fedora_test_page: => mark: => 0 milestone: SSSD 1.14 => NEEDS_TRIAGE review: => 0 selected: => sensitive: => 0
Upstream does not plan on implementing this ticket.
resolution: => wontfix status: new => closed
Metadata Update from @jhrozek: - Issue set to the milestone: NEEDS_TRIAGE
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2365
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.