same issue for us. Glad I am not the only one.
We use raw / distributed setup. ~1k hosts with ~30k services on ~16 sites all on debian 10.
Only difference is our master is on 2.0p15, cant upgrade to anything beyond that. Becomes completely unusable. I can upgrade the remote sites however.
I really dont want to turn off livestatus encryption.
Have a look at the directory structure. The real file is /opt/omd/versions/$version/lib/python3/livestatus.py
with /opt/omd/sites/$site/version being a symlink to …/…/versions/$version
So the file itself will not be touched by an upgrade (only by a reinstall of the same version). But the active symlink will then point to the unmodified file from the newly installed upgrade version. If the upgrade doesn’t already include the fix, then the change will have to be applied again.
This is the reason why one normally shouldn’t modify any code outside the site’s local hierarchy.