Yea it's odd. On the index system, restarting the service continued to fail until I figured out it was failing on not being able to read the keytab, after which I updated ownership and mode to root:sssd 0640. On another system just now I was able to restart SSSD and it started back up fine with root:root 0600.
I suppose it doesn't help that we're only a couple weeks into deploying 26.04 and have a comparably tiny sample size. I'll be keen to see if anyone else pops into the comments with their experiences. Otherwise I think this can be marked as not a bug. Thanks again for all the detailed comments, if anything it's at least given me a better understanding of these aspects of SSSD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155002 Title: Update to SSSD 2.12.0-1ubuntu5 breaks AD join due to SSSD inability to read keytab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2155002/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
