URL: https://github.com/SSSD/sssd/pull/655 Title: #655: Invalid id provider prevents other domains to start
mzidek-rh commented: """ TLDR: I will update the PR :) Actually I think there are two issues here. One is that the domain has invalid config that prevents it to start (bad id provider). This should be IMO solved the way I proposed (but more generic for example by checking if the .so module exists) in the confdb_get_domain_internal function. This allows us to skip this domain ctx everywhere (as I mentioned before even in other backends). This is what we also do for invalid ranges which is very similar error in nature (bad config option). The second issue (and arguably more important) is that failing to start one backend (for whatever reason) made sssd send SIGTERM to all backends. I think the problem here is in the dp_init_* family of functions (or where the return value of them is processed) but I am not sure. The current patches do not address this issue at all. So even after updating the current patch to be more generic we still need one more patch for this issue. While I see them as two issues they should be solved in the same patchset, because by fixing the first one we would lose a simple reproducer for the second issue. """ See the full comment at https://github.com/SSSD/sssd/pull/655#issuecomment-420585739
_______________________________________________ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahosted.org