Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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):
sssd-1.11.2-40.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Execute "# systemctl reload sssd" and see the failure.
man systemctl says:
reload NAME...
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
commands.
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.
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.