#3330 sssctl config-check does not give any error when default configuration file is not present
Closed: Fixed Opened by lslebodn.

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

Description of problem:
sssctl config-check does not give any error when default configuration file
(sssd.conf) is not present.
Version-Release number of selected component (if applicable):
sssd-1.15.1-1.el7.x86_64.
How reproducible:
Always.
Steps to Reproduce:
1. yum install -y sssd sssd-tools.
2. Create sssd.conf.
3. Start sssd service.
4. Remove sssd.conf file.
5. Before restart of sssd, run sssctl config-check.
Actual results:
Not giving any error message when there is no sssd.conf file.
Expected results:
sssctl config-check should give the some error message when default
configuration file is not present.

Metadata Update from @lslebodn:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1432112

Metadata Update from @lslebodn:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1432112

Metadata Update from @mzidek:
- Custom field rhbz reset
- Issue set to the milestone: None

sssd-1-14:

  • b35d7aa90b18ba544ba11fcabeb9662e38fb91fa

We need different message for 1.15; because missing configuration file is not critical for sssd-1.15

Metadata Update from @jhrozek:
- Issue assigned to mzidek

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.3

Metadata Update from @jhrozek:
- Issue priority set to: minor

master:

  • 955574eeb3a3b937abc3df150e9bbbb79b75c889

Message for master will change together with fixing #3339

Metadata Update from @lslebodn:
- Custom field version adjusted to 1.14.0

Metadata Update from @lslebodn:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

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

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.

Metadata