Our existing patroni setup was using patroni:12-latest image tag and stopped working over the last few days (uncertain exactly when, was working Sept. 30, 2021) and
logs showed standard python3.9 error about a missing package.
This image uses python3.9 and is missing the pip package named six.
The older image had python3.7 and the pip package named six was present.
To help troubleshoot this, I managed to update my stateful set to use an older image by sha from our imagestream and things started working fine again.
I created a new pod in my tools ns and ensured these lines were present in my yaml
command:
- /bin/bash
- '-c'
- '--'
args:
- while true; do sleep 30; done;
image: image-registry.openshift-image-registry.svc:5000/MYNS-tools/patroni:12-latest
then used terminal to check paths:
ls /usr/local/lib/python3.9/dist-packages
ls /usr/local/lib/python3.7/dist-packages
if you don't see a module named six.py or six* it's likely on the python3.9 image.
Please fix this or help us understand how this could happen!
Our existing patroni setup was using patroni:12-latest image tag and stopped working over the last few days (uncertain exactly when, was working Sept. 30, 2021) and logs showed standard python3.9 error about a missing package. This image uses python3.9 and is missing the pip package named six. The older image had python3.7 and the pip package named six was present.
To help troubleshoot this, I managed to update my stateful set to use an older image by sha from our imagestream and things started working fine again.
I created a new pod in my tools ns and ensured these lines were present in my yaml
then used terminal to check paths:
if you don't see a module named six.py or six* it's likely on the python3.9 image.
Please fix this or help us understand how this could happen!