https://bugzilla.redhat.com/show_bug.cgi?id=2078243
Bug ID: 2078243 Summary: sssd.conf files not came with sssd-common package anymore and service fails. Product: Fedora Version: 36 Status: NEW Component: sssd Assignee: sssd-maintainers@lists.fedoraproject.org Reporter: thunderbirdtr@gmail.com QA Contact: extras-qa@fedoraproject.org CC: abokovoy@redhat.com, atikhono@redhat.com, jhrozek@redhat.com, lslebodn@redhat.com, luk.claes@gmail.com, mzidek@redhat.com, pbrezina@redhat.com, sbose@redhat.com, ssorce@redhat.com, sssd-maintainers@lists.fedoraproject.org Target Milestone: --- Classification: Fedora
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.
https://bugzilla.redhat.com/show_bug.cgi?id=2078243
Fedora Blocker Bugs Application blockerbugs@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1953786 | |(F36FinalFreezeException,Fi | |nalFreezeException)
--- Comment #1 from Fedora Blocker Bugs Application blockerbugs@fedoraproject.org --- 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_servi...
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1953786 [Bug 1953786] Fedora 36 Final freeze exception bug tracker
https://bugzilla.redhat.com/show_bug.cgi?id=2078243
Geraldo Simião geraldo.simiao.kutz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |geraldo.simiao.kutz@gmail.c | |om
--- Comment #2 from Geraldo Simião geraldo.simiao.kutz@gmail.com --- 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
https://bugzilla.redhat.com/show_bug.cgi?id=2078243
Sumit Bose sbose@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Doc Type|--- |If docs needed, set a value
--- Comment #5 from Sumit Bose sbose@redhat.com --- 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
https://bugzilla.redhat.com/show_bug.cgi?id=2078243
Pavel Březina pbrezina@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed| |2022-04-25 08:56:58
--- Comment #6 from Pavel Březina pbrezina@redhat.com --- I'm closing this as not a bug, please disable sssd if you don't use it anymore or create /etc/sssd/sssd.conf.
sssd-maintainers@lists.fedoraproject.org