Comment 13 for bug 1812324

This bug is related to https://github.com/ansible/ansible/issues/45852 which seems to be the main reason why we encountered it.

Still, we had to workaround it because Ansible bug is not yet fixed and even when it will be fixed it would likely not be ported back to our version.