After some discussion with the team, I'm marking this as Won't Fix.
Increasing the StartLimitIntervalSec to any arbitrary value (even when
following upstream) does not really fix the issue generally, but only
for specific scenarios. The value can (and should) be tweaked by the
sysadmin to account for the specific situation they are encountering.
For future reference, this can be done with a systemd override file. In
/etc/systemd/system/sssd.override.d/, create a override.conf with the
desired values. E.g:
```
[Unit]
StartLimitIntervalSec=50s
StartLimitBurst=5
```
Tweak the values if needed.
** Changed in: sssd (Ubuntu Jammy)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122722
Title:
SSSD systemd service unit causes a boot loop in certain circumstances
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2122722/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
