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:
sssctl config-check giving the wrong error message when there are only snippet files and no sssd. conf
Version-Release number of selected component (if applicable):
sssd-2.0.0-38.el8.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create snippet file under /etc/sssd/conf.d
2. change the ownership and permissions to root:root and 600
3. Start the sssd service
4. Check user lookup
5. Run # sssctl config-check
Actual results:
# sssctl config-check
File /etc/sssd/sssd.conf does not exist. SSSD will use default configuration with files provider.
File ownership and permissions check failed. Expected root:root and 0600.
Expected results:
Here snippet file is added with proper ownership and permission and sssd does not use the default configuration as files provider.
Additional info:
# ll /etc/sssd/conf.d/01.conf
-rw-------. 1 root root 381 Jan 15 08:15 /etc/sssd/conf.d/01.conf
# cat /etc/sssd/conf.d/01.conf
[sssd]
config_file_version = 2
domains = LDAP
services = nss, pam
[domain/LDAP]
ldap_search_base = dc=example,dc=com
debug_level = 9
id_provider = ldap
auth_provider = ldap
ldap_user_home_directory = /home/%u
ldap_uri = ldaps://server.example.com:636
ldap_tls_cacert = /etc/openldap/certs/cacert.pem
use_fully_qualified_names = True
[nss]
[pam]
# getent passwd testuser@LDAP
testuser@LDAP:*:14583101:14564100:testuser User::/bin/bash
Just a note. This issue is about bad debug message.
# sssctl config-check
File /etc/sssd/sssd.conf does not exist. SSSD will use default configuration with files provider.
File ownership and permissions check failed. Expected root:root and 0600.
It should not say that the files domain will be used, because it may be not be (if snippets override it and create a different domain). Also the ownership and permissions check is confusing in this case and the message should probably not be printed at all.
Michal
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1863