#3470 sssd-kcm crashes with multiple parallel requests
Closed: worksforme by jhrozek. Opened by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1465457

Description of problem:
sssd_kcm crashes when kinit is run by multiple users repetitively (in a loop).
Version-Release number of selected component (if applicable):
sssd-client-1.15.2-50.el7.x86_64
sssd-ipa-1.15.2-50.el7.x86_64
sssd-proxy-1.15.2-50.el7.x86_64
python-sssdconfig-1.15.2-50.el7.noarch
sssd-common-1.15.2-50.el7.x86_64
sssd-common-pac-1.15.2-50.el7.x86_64
sssd-ad-1.15.2-50.el7.x86_64
sssd-ldap-1.15.2-50.el7.x86_64
sssd-1.15.2-50.el7.x86_64
sssd-kcm-1.15.2-50.el7.x86_64
sssd-krb5-common-1.15.2-50.el7.x86_64
sssd-krb5-1.15.2-50.el7.x86_64
libtevent-0.9.31-1.el7.x86_64
libtalloc-2.1.9-1.el7.x86_64
How reproducible:
Steps to Reproduce:
1. Join RHEL4 system to Windows AD using realm
2. Enable sssd-kcm
3.
sssd.conf
[sssd]
config_file_version = 2
services = nss, pam
domains = centaur.test
[domain/centaur.test]
ad_domain = centaur.test
krb5_realm = CENTAUR.TEST
cache_credentials = True
id_provider = ad
krb5_store_password_if_offline = True
default_shell = /bin/bash
ldap_id_mapping = True
use_fully_qualified_names = True
fallback_homedir = /home/%u@%d
ldap_id_mapping = True
access_provider = ad
enumerate = True
debug_level = 6
[pam]
debug_level = 9
[ssh]
[sudo]
[kcm]
debug_level = 9
4. Create 3 users in AD (foobar1, foobar2, foobar3 with password Secret123)
Open 3 terminals and run the below in parallel
#/bin/bash
export KRB5CCNAME=KCM:
date
echo Secret123 | kinit foobar1
date;for i in $(seq 1 100); do klist -A; done
On terminal 2
export KRB5CCNAME=KCM:
date
echo Secret123 | kinit foobar2
date;for i in $(seq 1 100); do klist -A; done
On terminal 3 run,
export KRB5CCNAME=KCM:
date
echo Secret123 | kinit foobar3
date;for i in $(seq 1 100); do klist -A; done
Actual results:
sssd-kcm crashes.
Expected results:
sssd-kcm should not crash.
Additional info:
Refer: https://bugzilla.redhat.com/show_bug.cgi?id=1446302#c11

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1465457

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1465457

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15 backlog)

Check downstream comments https://bugzilla.redhat.com/show_bug.cgi?id=1446302#c11
and https://bugzilla.redhat.com/show_bug.cgi?id=1446302#c26

Metadata Update from @jhrozek:
- Issue priority set to: major

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.15.4)

I tend to do a lot of ssh calls in a loop and such, which can provoke this bug rather easily.

Metadata Update from @lslebodn:
- Issue tagged with: KCM

Metadata Update from @jhrozek:
- Issue tagged with: bug, postpone-to-1-16-2

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.2 (was: SSSD 1.16.1)

Metadata Update from @jhrozek:
- Issue untagged with: postpone-to-1-16-2

Metadata Update from @fidencio:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Sorry, wrongly closed this PR. :-/

Metadata Update from @fidencio:
- Issue status updated to: Open (was: Closed)

Since we are near the 1.16.2 release and this ticket has no PR yet, it will slip into 1.16.3.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.3 (was: SSSD 1.16.2)

Metadata Update from @fidencio:
- Issue assigned to fidencio

Metadata Update from @fidencio:
- Assignee reset

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.4 (was: SSSD 1.16.3)

We could not reproduce this with a recent version, closing

Metadata Update from @jhrozek:
- Issue close_status updated to: worksforme
- Issue status updated to: Closed (was: Open)

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

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