#3209 No sssctl commands can be run if the configuration has fatal errors
Closed: Fixed None Opened 4 years ago by jhrozek.

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

Description of problem:
This bug found during the sssd test day for  rhel 7.3 features.

Multiple mistakes in sssd.conf :
    a. typo: id provider (sid provider)
    b. domains: default (removed)

Error: no domains configured
# sssctl config-check
(Tue Sep 13 14:59:27:675033 2016) [sssd] [confdb_get_domains] (0x0010): No
domains configured, fatal error!

Answer (Michal): This is expected in the current version. No sssctl commands
can be run (including config-check) if the configuration has fatal errors
(errors preventing SSSD from starting). This is suboptimal, especially for
command like config-check. Please file a BZ or upstream ticket, so that we
enhance this in the future version.


Version-Release number of selected component (if applicable):
sssd-1.14.0-43.el7.x86_64.rpm

Assigning to Fabiano because he already has a patch in a PR on github.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD 1.15 Beta
owner: somebody => fidencio
review: True => 0
selected: =>
testsupdated: => 0

Err, sorry, wrong ticket.

milestone: SSSD 1.15 Beta => SSSD 1.14.2
owner: fidencio => mzidek

Fields changed

patch: 0 => 1

Moving tickets that didn't make it into the 1.14.2 release into the next point release.

milestone: SSSD 1.14.2 => SSSD 1.14.3

master:

sssd-1-14:

LS

resolution: => fixed
status: new => closed
version: => 1.14.0

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.14.3

3 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/4242

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