Created attachment 1917056 [details] /tmp/syslog from installer environment Description of problem: We have new CRIT error messages appearing in kickstart during root password setup in chroot (and also in one other place): 09:32:55,063 WARNING org.fedoraproject.Anaconda.Modules.Users:INFO:anaconda.modules.common.task.task:Configure root password 09:32:55,136 WARNING org.fedoraproject.Anaconda.Modules.Users:INFO:program:Running... chpasswd -R /mnt/sysroot -e 09:32:55,267 CRIT sss_cache:No domains configured, fatal error! 09:32:55,317 CRIT sss_cache:No domains configured, fatal error! 09:32:55,328 WARNING org.fedoraproject.Anaconda.Modules.Users:INFO:program:Running... chage -R /mnt/sysroot -d root 09:32:55,402 NOTICE audit:USER_MGMT pid=20479 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='op=change-last-change-date id=0 exe="/usr/bin/chage" hostname=? addr=? terminal=? res=success' 09:32:55,499 CRIT sss_cache:No domains configured, fatal error! 09:32:55,515 WARNING org.fedoraproject.Anaconda.Modules.Users:INFO:program:[sss_cache] [confdb_get_domains] (0x0010): No domains configured, fatal error! 09:32:55,515 WARNING org.fedoraproject.Anaconda.Modules.Users:DEBUG:program:Return code: 0 Version-Release number of selected component (if applicable): https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/COMPOSE_ID: Fedora-Rawhide-20221009.n.0 It seems to start happening when sssd-2.8.0-1 replaced sssd-2.7.4-1. Are we missing some configuration in installation environment? How reproducible: Do Fedora Server installation with latest development rawhide Steps to Reproduce: 1. 2. 3. Actual results: Error messages in the log, but installation seems to finish without issues. Expected results: No CRIT error messages by sss in the logs. Additional info: The CRIT messages make Anaconda kickstart test fail. We can put them on a ignore list but we should try to fix the origin of the messages first.
Hi, do you have anything under `/etc/sssd/`?
(In reply to Alexey Tikhonov from comment #1) > Hi, > > do you have anything under `/etc/sssd/`? Most probably there is no and I can confirm change of behavior of `sss_cache` in this case. Probably the reason is https://github.com/SSSD/sssd/commit/003b94fb382c18784831adc03afa1a5860f760d0 that made `confdb_get_enabled_domain_list()` to return `ENOENT` and this results in sys log message https://github.com/SSSD/sssd/blob/master/src/confdb/confdb.c#L1803
(In reply to Alexey Tikhonov from comment #2) > (In reply to Alexey Tikhonov from comment #1) > > Hi, > > > > do you have anything under `/etc/sssd/`? In the installer environment there is no /etc/sssd at all. The chpasswd and change command are run in the installer environment, so without the config files.
Upstream PR: https://github.com/SSSD/sssd/pull/6388
Pushed PR: https://github.com/SSSD/sssd/pull/6388 * `master` * df55b1f16ea2fb5e56f0fe69419904d50b7e2476 - confdb: chande debug level when no domain are found in confdb_get_domains * 64c22dd1c4f79f953b879fc167b535de928f4bfd - sss_cache: use ERR_NO_DOMAIN_ENABLED instead of ENOENT * 4da861368b88c03b22993f95de5b508ad5637c25 - monitor: read all enabled domains in add_implicit_services * b38fdc8185fcd6a2e5d4b483d3119964f9922070 - confdb: avoid syslog message when no domains are enabled * `sssd-2-8` * ab7cbb5f0f74e5061136cf632f487d7a8c023272 - confdb: chande debug level when no domain are found in confdb_get_domains * a6312c46daebcf39b9331cc2c99f5abfe25f64d0 - sss_cache: use ERR_NO_DOMAIN_ENABLED instead of ENOENT * 1df029470df8af58cf63e41bdad7b8882b141ac3 - monitor: read all enabled domains in add_implicit_services * a6d521458460593afc7585f2d269aa4c6f326ecb - confdb: avoid syslog message when no domains are enabled
FEDORA-2022-34184a1bbe has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-34184a1bbe
FEDORA-2022-34184a1bbe has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-34184a1bbe` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-34184a1bbe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-34184a1bbe has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.