#1274 Wrong resolv_status might cause crash when name resolution times out
Closed: Fixed Opened by jhrozek.

When name resolution times out, the errno return code is 110 (which is correct = ETIMEDOUT), but the resolv_status is 0. This is wrong.

We should probably rely mostly on the errno return code and only treat the resolv_status, which is the original ares return code, as kind of extended information, also because in the future we might switch to a different resolver with different error codes.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.8.2 (LTM)

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=805918

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=805918 805918]

Fields changed

patch: 0 => 1
status: new => assigned

Fixed by:
- 64f398dca52df6313169f33cfc20a69d51c3bc2b (master)
- bd0dad92d8cd37f9c710741a33820368d9a831c5 (sssd-1-8)

resolution: => fixed
status: assigned => closed

Fields changed

component: SSSD => Async Resolver

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=812387 (Fedora)

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=805918 805918] => [https://bugzilla.redhat.com/show_bug.cgi?id=805918 805918], [https://bugzilla.redhat.com/show_bug.cgi?id=812387 812387]

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.8.2 (LTM)

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/2316

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata