Description of problem:
Command "systemctl reload sssd" fails with the following error:
Failed to issue method call: Job type reload is not applicable for unit sssd.service.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Execute "# systemctl reload sssd" and see the failure.
man systemctl says:
Asks all units listed on the command line to reload their
configuration. Note that this will reload the service-specific
configuration, not the unit configuration file of systemd. If you
want systemd to reload the configuration file of a unit, use the
daemon-reload command. In other words: for the example case of
Apache, this will reload Apache's httpd.conf in the web server, not
the apache.service systemd unit file.
This command should not be confused with the daemon-reload or load
SSSD does not implement reloading configuration on the fly. If you want to reload configuration you will need to restart sssd.
I would say this is not a bug but only RFE
(In reply to Lukas Slebodnik from comment #1)
> I would say this is not a bug but only RFE
Right, we could implement an ExecReload=pkill -HUP sssd or something similar, but I don't think it's needed.
As agreed on the SSSD meeting on 03-27, this bug should be looked at when we work on socket activating the services. For now, I'll re-propose for 7.1 to get the bz off the 7.0 radar.
Although Simo is working on socket-activating the Custodia responder, we don't plan on making all services socket activatable by default, so this bugzilla should be looked at again in the 7.4 timeframe.
Upstream ticket #2243 is fixed but "systemctl reload" is not implemented there.
I don't think we will implement systemctl reload per se, so I'm going to close this ticket.
What would IMO make value to track in RHEL is https://pagure.io/SSSD/sssd/issue/3352 instead.