I took a look at this with the reporter this afternoon. Looks like a simple missing NULL-check. I've got a patch that I'm having the reporter test and then I'll send it to the list.

component: SSSD => AD Provider
description: Following a 1.11.4 to 1.11.5 upgrade on Ubuntu, all my sssd daemons crashed.

After debugging on IRC, this appears to be caused by a wrong assumption that the forest name can be NULL.

backtrace: http://paste.ubuntu.com/7228102/
backtrace (full): http://paste.ubuntu.com/7228168/
config in use: http://paste.ubuntu.com/7228110/
log (-d 9): http://paste.ubuntu.com/7228126/
extract of the forest value: http://paste.ubuntu.com/7228178/ => Following a 1.11.4 to 1.11.5 upgrade on Ubuntu, all my sssd daemons crashed.

After debugging on IRC, this appears to be caused by a wrong assumption that the forest name can be NULL.

• backtrace: http://paste.ubuntu.com/7228102/
• backtrace (full): http://paste.ubuntu.com/7228168/
• config in use: http://paste.ubuntu.com/7228110/
• log (-d 9): http://paste.ubuntu.com/7228126/
• extract of the forest value: http://paste.ubuntu.com/7228178/
  owner: somebody => sgallagh
  status: new => assigned

• master: 8653b54
• sssd-1-11: 4140552

I'll leave the ticket open for our triage.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.6
rhbz: => 0

Fields changed

resolution: => fixed
status: assigned => closed

Fields changed

milestone: SSSD 1.11.6 => SSSD 1.11.5.1

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1091957 (Red Hat Enterprise Linux 7)

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

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

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.