Bug 985732
| Summary: | [RFE] sssd service restart fails when reconfigured too quickly - provide way to display status | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | David Spurek <dspurek> |
| Component: | sssd | Assignee: | SSSD Maintainers <sssd-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Kaushik Banerjee <kbanerje> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | dsulliva, grajaiya, jgalipea, jhrozek, joallen, mkosek, pbrezina, pkis |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-04-23 09:06:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1044717, 1113520, 1133060 | ||
|
Description
David Spurek
2013-07-18 06:14:27 UTC
Jakub, is there a better way to tell sssd to reload its config than to restart it? It seems like systemd doesn't like rapid restarts of sssd. (In reply to Stef Walter from comment #2) > Jakub, is there a better way to tell sssd to reload its config than to > restart it? It seems like systemd doesn't like rapid restarts of sssd. Currently there is not. We had this possibility a long time ago where the SSSD could re-read its config after receiving SIGHUP, but it was fragile and nobody seemed to be interested. Maybe we could have a lightweight version of the dynamic re-reading that would only check new access control parameters. I wonder if there is a real use-case, though or whether this is mostly useful in unit tests.. The real use case is questionable, but I think realmd should at least check the status of the restarted service and return an error if it failed to properly restart such a key service as sssd. sssd provides no tool to restart the sssd daemon. We use the systemctl command. systemctl merely sends a signal to systemd to restart the service. We have no way of knowing: a) Whether systemd allowed the service to restart b) If sssd initialized correctly c) If sssd went online correctly I would love realmd to be able to have more interaction with the startup and status of sssd. However currently sssd provides no such interface. It's a black box in that respect. Reassigning, and interested in discussing further about how sssd could provide some of the needed interfaces for this sort of thing. (In reply to Stef Walter from comment #5) > sssd provides no tool to restart the sssd daemon. We use the systemctl > command. systemctl merely sends a signal to systemd to restart the service. > > We have no way of knowing: > > a) Whether systemd allowed the service to restart This should be handled by systemctl, in particular the error code it returns. I'm not sure SSSD has a way of knowing either.. > b) If sssd initialized correctly Current versions of the SSSD wait until the responders and back ends start (or not). Then you can inspect the systemctl return code as well. I just tested by configuring a bogus "id_provider" value. Maybe we could hint more verbosly into the syslog/journal/whatever? > c) If sssd went online correctly > Right, this is a separate issue that we avoided for quite some time, but it's coming up again and again, so it sounds like we might want to do at least some best-effort fix. I would prefer to go with a status tool (see below). > I would love realmd to be able to have more interaction with the startup and > status of sssd. However currently sssd provides no such interface. It's a > black box in that respect. > > Reassigning, and interested in discussing further about how sssd could > provide some of the needed interfaces for this sort of thing. In general, I think we need to prioritize work on something like the "sssctl" tool we talked about a while ago. Some kind of richer interface towards the SSSD that would allow to query the status of back ends, what back ends started etc. There is some discussion summarized in this upstream ticket: https://fedorahosted.org/sssd/ticket/1828 Upstream ticket: https://fedorahosted.org/sssd/ticket/385 This issue is now tracked in bug 879333 *** This bug has been marked as a duplicate of bug 879333 *** |