Comment 30 for bug 1844929

> This behavior of not "resetting" or sanitizing standard library locks at fork is a known issue in python [2] that's currently being worked on.

Correction: this issue [3] is not considered a bug in python and the recommended way of handling the problem is to use the os.register_at_fork() method (new in python 3.7) in oslo.db to reinitialize its lock [4].

For now, we still support python 3.6, so we have to handle it outside of oslo.db some way. But we can also add use of os.register_at_fork() in oslo.db for those who are running >= python 3.7 to handle the problem more generally.

[3] https://bugs.python.org/issue6721
[4] https://bugs.python.org/issue40091#msg365959