We're seeing this behavior on 3.2.10 with the patch from bug 1848550 backported and installed. I suspect that patch could be a proximal cause of this issue. Hopefully, that can help find a solution.
We're seeing this behavior on 3.2.10 with the patch from bug 1848550 backported and installed. I suspect that patch could be a proximal cause of this issue. Hopefully, that can help find a solution.