https://bugzilla.suse.com/show_bug.cgi?id=1188999 https://bugzilla.suse.com/show_bug.cgi?id=1188999#c1 Samuel Cabrero <scabrero@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Samuel Cabrero <scabrero@suse.com> --- Hi Luiz, I have reproduced it but sssd behaves as intended because the sssd.service file contains "Restart=on-failure" to fix https://github.com/SSSD/sssd/issues/5009. A possible workaround would be to automatically join the domain using a script block in the autoyast profile, or add StartLimitIntervalSec and StartLimitBurst as an override for sssd.service. You could also open an upstream bug in https://github.com/SSSD/sssd/issues to add StartLimitIntervalSec and StartLimitBurst to sssd.service file (3 starts in 30 seconds limit works for me). Finally, with regards to systemd spamming over yast ncursers I encourage you to open a separate bug for the YaST component. Do not hesitate to reopen if you have more questions or problems. -- You are receiving this mail because: You are on the CC list for the bug.