I freshly installed Fedora KDE 36 on VM and "sssd" service gives "condition failed" error. I have some problem on my current F36 machine as well. Package versions: sssd-common-2.6.3-1.fc36.x86_64 sssd-2.6.3-1.fc36.x86_64 Service Result systemctl status sssd ○ sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not met I removed directory and re-installed and none of them worked. rpm -ql sssd-common | grep etc /etc/logrotate.d /etc/logrotate.d/sssd /etc/pam.d/sssd-shadowutils /etc/rwtab.d /etc/rwtab.d/sssd /etc/sssd /etc/sssd/conf.d /etc/sssd/pki /etc/sssd/sssd.conf Normally, I expect it should be up and running.
Proposed as a Freeze Exception for 36-final by Fedora user thunderbirdtr using the blocker tracking app because: SSSD service won't starting on default installation because file is missing, It either needs to be stop at default or config file must be restored. I believe this is violating "system service" criterion. ``` All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present. ``` https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#System_services
Same here on an baremetal instalation (acer aspire notebook) systemctl status sssd ○ sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Sun 2022-04-24 21:04:16 -03; 1h 10min ago ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not met systemd[1]: sssd.service - System Security Services Daemon was skipped because all trigger condition checks failed. $ rpm -qa|grep sssd sssd-nfs-idmap-2.7.0-1.fc36.x86_64 sssd-client-2.7.0-1.fc36.x86_64 sssd-common-2.7.0-1.fc36.x86_64 sssd-krb5-common-2.7.0-1.fc36.x86_64 sssd-common-pac-2.7.0-1.fc36.x86_64 sssd-krb5-2.7.0-1.fc36.x86_64 sssd-ldap-2.7.0-1.fc36.x86_64 sssd-idp-2.7.0-1.fc36.x86_64 sssd-proxy-2.7.0-1.fc36.x86_64 sssd-ad-2.7.0-1.fc36.x86_64 sssd-ipa-2.7.0-1.fc36.x86_64 sssd-2.7.0-1.fc36.x86_64 sssd-kcm-2.7.0-1.fc36.x86_64 $ rpm -ql sssd-common | grep etc /etc/logrotate.d /etc/logrotate.d/sssd /etc/pam.d/sssd-shadowutils /etc/rwtab.d /etc/rwtab.d/sssd /etc/sssd /etc/sssd/conf.d /etc/sssd/pki /etc/sssd/sssd.conf Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.17.4-300.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000
tested with the Fedora-KDE-Live-x86_64-36-1.1.iso on VM and got the same results as Onuralp, same package versions too (sssd-common-2.6.3-1.fc36.x86_64 sssd-2.6.3-1.fc36.x86_64)
Tryed to star manualy the service (sudo systemctl start sssd) but didn't worked.
Hi, this is expected behavior since Fedora 35. If there is no explicit configuration SSSD is not started anymore. Before SSSD started even if there was not configuration file and handled looks for users and groups from /etc/passwd and /etc/group, respectively. It turned out that the benefits of this were less than hoped and it was disabled in Fedora 35 by change https://fedoraproject.org/wiki/Changes/FlexibleLocalUserCache. HTH bye, Sumit
I'm closing this as not a bug, please disable sssd if you don't use it anymore or create /etc/sssd/sssd.conf.