Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1711832
(Adding Sumit's investigation)
It is an issue with the files provider which does not expect to ever be offline and hence does not handle the resetOffline request from the monitor. If the files provider runs with a different provider and the provider goes offline and back online the files provider might get a resetOffline as well and crash as you have seen it because 'ctx->check_if_online_ptask' is NULL and there is no NULL check in be_ptask_disable()..
To reproduce this easily you can start SSSD with the file provider, it can even be the implicit files provider which is started without any SSSD configuration and send SIGUSR2 to the sssd monitor process.
Per thalman, we should check the task parameter in be_ptask_(enable|disable)
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1711832
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1711832, https://bugzilla.redhat.com/show_bug.cgi?id=1711832 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1711832)
Issue linked to Bugzilla: Bug 1711832
PR: https://github.com/SSSD/sssd/pull/818
Metadata Update from @sbose: - Custom field patch adjusted to on
Commit 2720d97 relates to this ticket
Metadata Update from @jhrozek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @jhrozek: - Issue assigned to sbose - Issue set to the milestone: SSSD 2.2 - Issue tagged with: bug
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/4985
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.
Login to comment on this ticket.