I'm starting to take a look at this bug, and the first step here is to find a reproducer for it. This is needed because the bug affects stable releases of Ubuntu, so we will need to go through the SRU process in order to update sssd, and the process requires (among other things) that we provide a clear Test Plan for the bug.
I understand that the problem happens when sssd is being shutdown after socket-activated services are started. I'm wondering if you have any reproducer handy there. So far I haven't been able to trigger the error, but I will keep investigating.
Hello Todd,
I'm starting to take a look at this bug, and the first step here is to find a reproducer for it. This is needed because the bug affects stable releases of Ubuntu, so we will need to go through the SRU process in order to update sssd, and the process requires (among other things) that we provide a clear Test Plan for the bug.
I understand that the problem happens when sssd is being shutdown after socket-activated services are started. I'm wondering if you have any reproducer handy there. So far I haven't been able to trigger the error, but I will keep investigating.
Thanks.