https://bugzilla.redhat.com/show_bug.cgi?id=2291235
--- Comment #8 from Alexander Bokovoy abokovoy@redhat.com --- It was OK at 14:14:16:
Jun 10 14:14:16 ipa001 systemd[1]: Starting sssd.service - System Security Services Daemon... Jun 10 14:14:16 ipa001 sssd[9257]: Starting up Jun 10 14:14:16 ipa001 sssd_be[9258]: Starting up Jun 10 14:14:16 ipa001 sssd_ssh[9263]: Starting up Jun 10 14:14:16 ipa001 sssd_sudo[9264]: Starting up Jun 10 14:14:16 ipa001 sssd_nss[9259]: Starting up Jun 10 14:14:16 ipa001 sssd_ifp[9262]: Starting up Jun 10 14:14:16 ipa001 sssd_pam[9260]: Starting up Jun 10 14:14:16 ipa001 sssd_pac[9265]: Starting up Jun 10 14:14:16 ipa001 systemd[1]: Started sssd.service - System Security Services Daemon.
Stopped during system upgrade at 14:21:00:
Jun 10 14:21:00 ipa001 sssd_ifp[9262]: Shutting down (status = 0) Jun 10 14:21:00 ipa001 sssd_pam[9260]: Shutting down (status = 0) Jun 10 14:21:00 ipa001 sssd_ssh[9263]: Shutting down (status = 0) Jun 10 14:21:00 ipa001 sssd_sudo[9264]: Shutting down (status = 0) Jun 10 14:21:00 ipa001 sssd_pac[9265]: Shutting down (status = 0) Jun 10 14:21:00 ipa001 sssd_nss[9259]: Shutting down (status = 0) Jun 10 14:21:00 ipa001 systemd[1]: Stopping systemd-homed-activate.service - Home Area Activation... Jun 10 14:21:00 ipa001 sssd_be[9258]: Shutting down (status = 0) Jun 10 14:21:00 ipa001 systemd[1]: Started plymouth-reboot.service - Show Plymouth Reboot Screen. Jun 10 14:21:00 ipa001 systemd[1]: systemd-homed-activate.service: Deactivated successfully. Jun 10 14:21:00 ipa001 systemd[1]: Stopped systemd-homed-activate.service - Home Area Activation. Jun 10 14:21:00 ipa001 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=suc Jun 10 14:21:00 ipa001 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-homed-activate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? r Jun 10 14:21:00 ipa001 systemd[1]: sssd.service: Deactivated successfully. Jun 10 14:21:00 ipa001 systemd[1]: Stopped sssd.service - System Security Services Daemon.
Upgrade happened at 14:23:
Jun 10 14:23:12 ipa001 dnf-3[716]: Upgrading : sssd-common-pac-2.10.0~beta1-1.fc41.x86_64 430/2052 Jun 10 14:23:12 ipa001 dnf-3[716]: Upgrading : sssd-krb5-common-2.10.0~beta1-1.fc41.x86_64 431/2052 Jun 10 14:23:12 ipa001 dnf-3[716]: warning: group sssd does not exist - using root Jun 10 14:23:12 ipa001 dnf-3[716]: warning: group sssd does not exist - using root Jun 10 14:23:12 ipa001 dnf-3[716]: warning: user sssd does not exist - using root Jun 10 14:23:12 ipa001 dnf-3[716]: warning: group sssd does not exist - using root Jun 10 14:23:12 ipa001 dbus-broker-launch[715]: Noticed file-system modification, trigger reload. Jun 10 14:23:12 ipa001 dbus-broker-launch[715]: Noticed file-system modification, trigger reload. Jun 10 14:23:13 ipa001 dbus-broker-launch[715]: Noticed file-system modification, trigger reload. Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : libfprint-1.94.6-1.fc40.x86_64 432/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : fprintd-1.94.2-11.fc40.x86_64 433/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : python-pip-wheel-24.0-2.fc41.noarch 434/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : libssh-0.10.6-6.fc41.x86_64 435/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : python3-sssdconfig-2.10.0~beta1-1.fc41.noarch 436/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : sssd-ad-2.10.0~beta1-1.fc41.x86_64 437/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : sssd-ipa-2.10.0~beta1-1.fc41.x86_64 438/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: warning: group sssd does not exist - using root Jun 10 14:23:13 ipa001 dnf-3[716]: warning: user sssd does not exist - using root Jun 10 14:23:13 ipa001 dnf-3[716]: warning: group sssd does not exist - using root Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : sssd-krb5-2.10.0~beta1-1.fc41.x86_64 439/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : sssd-ldap-2.10.0~beta1-1.fc41.x86_64 440/2052 Jun 10 14:23:13 ipa001 dnf-3[716]: Upgrading : sssd-proxy-2.10.0~beta1-1.fc41.x86_64 441/2052
upgrade continues, so by 14:31:15 we were still in the upgrade path and at 14:32:55 we reboot second time:
Jun 10 14:32:55 ipa001 kernel: Linux version 6.10.0-0.rc2.20240607git8a92980606e3.28.fc41.x86_64 (mockbuild@7a76e6232d034e82aa1b8e85988de8da) (gcc (GCC) 14.1.1 20240522 (Red Hat 14.1.1-4), GNU ld version 2.42.50.20240513) #1 SMP PR
SSSD start is initiated at 14:33:01:
Jun 10 14:33:01 ipa001 systemd[1]: Starting sssd.service - System Security Services Daemon... Jun 10 14:33:02 ipa001 sssd[802]: Starting up Jun 10 14:33:02 ipa001 sssd_be[817]: Starting up Jun 10 14:33:02 ipa001 sssd_be[832]: Starting up Jun 10 14:33:04 ipa001 sssd_be[1003]: Starting up Jun 10 14:33:08 ipa001 sssd_be[1065]: Starting up Jun 10 14:33:08 ipa001 sssd[802]: Exiting the SSSD. Could not restart critical service [test.openqa.fedoraproject.org]. Jun 10 14:33:08 ipa001 systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE Jun 10 14:33:08 ipa001 systemd[1]: sssd.service: Failed with result 'exit-code'. Jun 10 14:33:08 ipa001 systemd[1]: Failed to start sssd.service - System Security Services Daemon.
It looks like something has happened to the /etc/krb5.keytab, at the very least...