CentOS - Dec 2022 - CentOS Stream 8 sssd.service failing part of sssd-common-2.8.1-1.el8.x86_64 baseos package

Hello everybody,

A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is causing 
sssd.service systemctl failures all over my CentosOS machines.

What is the best way to report this issue and when can we expect an 
update from the sssd-common package for this regression bug?

I think sssd-common is part of the baseos repository and installed even 
when the configuration file is not installed.

If someone can also provide more details on this issue I would 
appreciate it.

Thank you all in advance,

Kind regards,

Jelle de Jong

# cat /var/log/dnf.log | grep sssd-common
2022-11-25T06:29:42+0100 DEBUG Upgraded: sssd-common-2.7.3-5.el8.x86_64
2022-11-25T06:29:42+0100 DDEBUG 
/var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.7.3-5.el8.x86_64.rpm
removed
2022-11-26T06:08:38+0100 DEBUG Upgraded: sssd-common-2.7.3-5.0.1.el8.x86_64
2022-11-26T06:08:38+0100 DDEBUG 
/var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.7.3-5.0.1.el8.x86_64.rpm
removed
2022-12-25T06:23:42+0100 DEBUG Upgraded: sssd-common-2.8.1-1.el8.x86_64
2022-12-25T06:23:43+0100 DDEBUG 
/var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.8.1-1.el8.x86_64.rpm
removed

# cat /etc/os-release
NAME="CentOS Stream"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Stream 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"

# cat /var/log/sssd/sssd.log
(2022-12-25  6:23:34): [sssd] [monitor_quit_signal] (0x3f7c0): Monitor 
received Terminated: terminating children
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Returned with: 0
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating 
[nss][302626]
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [nss] 
terminated with a signal
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating 
[implicit_files][302625]
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child 
[implicit_files] terminated with a signal
[sssd] [confdb_expand_app_domains] (0x0010): No domains configured, 
fatal error!
[sssd] [get_monitor_config] (0x0010): Failed to expand application domains
[sssd] [confdb_get_domains] (0x0020): No domains configured, fatal error!
[sssd] [get_monitor_config] (0x0010): No domains configured.
[sssd] [main] (0x0010): SSSD couldn't load the configuration database 
[1432158246]: No domain is enabled

# cat /var/log/sssd/sssd.log
(2022-12-25  6:23:34): [sssd] [monitor_quit_signal] (0x3f7c0): Monitor 
received Terminated: terminating children
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Returned with: 0
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating 
[nss][302626]
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [nss] 
terminated with a signal
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating 
[implicit_files][302625]
(2022-12-25  6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child 
[implicit_files] terminated with a signal
[sssd] [confdb_expand_app_domains] (0x0010): No domains configured, 
fatal error!
[sssd] [get_monitor_config] (0x0010): Failed to expand application domains
[sssd] [confdb_get_domains] (0x0020): No domains configured, fatal error!
[sssd] [get_monitor_config] (0x0010): No domains configured.
[sssd] [main] (0x0010): SSSD couldn't load the configuration database 
[1432158246]: No domain is enabled

# systemctl status sssd
? sssd.service - System Security Services Daemon
    Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; 
vendor preset: enabled)
    Active: failed (Result: exit-code) since Sun 2022-12-25 06:23:35 
CET; 9h ago
  Main PID: 615303 (code=exited, status=4)

On 2022-12-25 07:44, Jelle de Jong wrote:
> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is 
> causing sssd.service systemctl failures all over my CentosOS machines.
...
> [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, 
> fatal error! 

Were you previously using sssd?? Or is the problem merely that it is now 
reporting an error starting a service that you don't use?

Are there any files in /etc/sssd/conf.d, or does /etc/sssd/sssd.conf 
exist?? If so, what are the contents of those files?

What are the contents of /usr/lib/systemd/system/sssd.service?

If you run "journalctl -u sssd.service", are there any log entries
older
than the package update?