pip-install.sh/coda-install.sh fails on cluster with version 2.2.31-debian12

[ivan-tsarev-bioage]

We have a cluster which we recreate daily for a small dbt model job and unfortunately, we had unpinned cluster version there.
Couple days ago it started to fail provisioning on pip-install.sh action with following error logs:

+ pip install --upgrade deepdiff==7.0.1
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f3d077682d0>: Failed to establish a new connection: [Errno 101] Network is unreachable')': /simple/deepdiff/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f3d09282b90>: Failed to establish a new connection: [Errno 101] Network is unreachable')': /simple/deepdiff/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f3d0776f550>: Failed to establish a new connection: [Errno 101] Network is unreachable')': /simple/deepdiff/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f3d0774e010>: Failed to establish a new connection: [Errno 101] Network is unreachable')': /simple/deepdiff/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f3d0779cc10>: Failed to establish a new connection: [Errno 101] Network is unreachable')': /simple/deepdiff/
ERROR: Could not find a version that satisfies the requirement deepdiff==7.0.1 (from versions: none)
ERROR: No matching distribution found for deepdiff==7.0.1

Cluster version with errors was 2.2.31-debian12.
After some random attempts to fix the issue within network settings and updating init-actions scripts to the latest versions, we managed to fix the issue just by pinning cluster version back to 2.1-debian11.
That led me to assumption that there is something wrong with the latest cluster version and python install actions.