Thanks for providing the full config files. I didn't try to setup a full reproducer, but this does seems to be valid bug. I have to say that we can't be sure of when we'll be able to begin working at this, as the specific setup (custom schema) means that the number of affected systems is likely low.
What can help speeding up the debugging work here is identifying a fix (e.g. in a newer upstream release of sssd), or at least finding out that the bug is not present in an older (or newer) Ubuntu release. Moreover, if the bug is still present in the devel release of Ubuntu (lunar-proposed packages sssd 2.8.1) there is a good chance that the bug is still present in the latest upstream release, so it may be worth filing it upstream [1]. If you do so please let us have a link to the upstream bug. Thanks!
Thanks Andreas (@ahasenack) for having a look at the config and logs.
Thanks for providing the full config files. I didn't try to setup a full reproducer, but this does seems to be valid bug. I have to say that we can't be sure of when we'll be able to begin working at this, as the specific setup (custom schema) means that the number of affected systems is likely low.
What can help speeding up the debugging work here is identifying a fix (e.g. in a newer upstream release of sssd), or at least finding out that the bug is not present in an older (or newer) Ubuntu release. Moreover, if the bug is still present in the devel release of Ubuntu (lunar-proposed packages sssd 2.8.1) there is a good chance that the bug is still present in the latest upstream release, so it may be worth filing it upstream [1]. If you do so please let us have a link to the upstream bug. Thanks!
Thanks Andreas (@ahasenack) for having a look at the config and logs.
[1] https:/ /github. com/SSSD/ sssd/issues