#2292 [RFE] Implement systemctl reload
Closed: Invalid None Opened 10 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1080960

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.

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
priority: major => trivial
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta
priority: trivial => minor
summary: RFE: implement systemctl reload => [RFE] Implement systemctl reload
type: defect => enhancement

Fields changed

mark: => 0

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the next two releases.

Please reply with a comment if you disagree about the move..

milestone: SSSD 1.13 backlog => SSSD 1.15 beta

I would defer.

review: 0 => 1
selected: => May
sensitive: => 0

For anyone interested in working on this feature -- we actually had code to provide reloads without restarts in sssd for some time already, but it was challenging for several reasons:
- reconfiguring an existing domain might not always be possible. Some configuration changes (like changes to ID mapping ranges) might even require the database to be removed
- some configuration parameters are read once after responder or provider startup and then just kept in memory
- even with reloading, there might be an inherent downtime when a new connection is re-established

Seeing those reasons again written down actually makes me wonder whether we should just close this ticket as wontfix..

So implementing the reload per se would be possible but the question is what to do during the reload. Traditionally it's been reloading the configuration which we tried to do in sssd a long time ago but never have gotten it to work reliably.

Therefore I'm closing the ticket. Please reopen with a better suggestion of what the reload might do, or even better, with patches.

resolution: => wontfix
status: new => closed

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

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/3334

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata