Switching the docker image failed:

tools.zppixbot-test@tools-sgebastion-07:~/zppixbottest/bin$ kubectl logs sopeltest.bot-7b7cc7c58-v6vgk
Traceback (most recent call last):
  File "/data/project/zppixbot-test/zppixbottest/bin/pip3", line 5, in <module>
    from pip._internal.cli.main import main
ModuleNotFoundError: No module named 'pip'
Traceback (most recent call last):
  File "/data/project/zppixbot-test/zppixbottest/bin/pip3", line 5, in <module>
    from pip._internal.cli.main import main
ModuleNotFoundError: No module named 'pip'
Traceback (most recent call last):
  File "/data/project/zppixbot-test/zppixbottest/bin/pip3", line 5, in <module>
    from pip._internal.cli.main import main
ModuleNotFoundError: No module named 'pip'
Traceback (most recent call last):
  File "/data/project/zppixbot-test/zppixbottest/bin/pip3", line 5, in <module>
    from pip._internal.cli.main import main
ModuleNotFoundError: No module named 'pip'
Traceback (most recent call last):
  File "/data/project/zppixbot-test/zppixbottest/bin/sopel", line 5, in <module>
    from sopel.cli.run import main
ModuleNotFoundError: No module named 'sopel'

Try https://community.home-assistant.io/t/how-to-upgrade-virtualenv-virtual-environment-to-python-3-7-on-ubuntu-ubuntu-server-18-04/145640

-test was done last night

For whoever does the docs:
/me looks at @MacFan4000
Steps:

• webservice python[version] shell
• python[version] -m venv [new venv name]
• python —version to check update
• Update the active shell file (currently starter-new.sh) to point to the new venv (check ls -lsa in [new venv name]/bin to see the name for the correct python/pip file)
• switch the yaml file (normally sopelbot.yaml) to the new image from docker registery
• kubectl delete deployment [name for the bot] & kubectl create --validate=true -f /data/project/[instance]/k8s/[yaml file]
• Then if everything goes well, delete the old venv

DO NOT ROLL THIS FORWARD UNTIL T254348: ZppixBot-test fails restarts correctly on python 3.7 after crash IS RESOLVED AND I HAVE CONFIRMED

Mentioned in SAL (#wikimedia-cloud) [2020-06-03T17:58:37Z] <RhinosF1> rolling back to python 3.5 with examknow due to T254348 cc T254246

Mentioned in SAL (#wikimedia-cloud) [2020-06-03T18:15:25Z] <RhinosF1> python is now 3.5 due to T254348 cc T254246

This should be unblocked by the end of today.

We'll be attempting to roll forward on Monday to -test + Wednesday to core.

I unstall this when I resolve the subtask tonight.

The venv is 'zbpy37'

Mentioned in SAL (#wikimedia-cloud) [2020-06-08T21:22:30Z] <RhinosF1> deleted sopel deployment to switch to py3.7 START -- T254246

Mentioned in SAL (#wikimedia-cloud) [2020-06-08T21:30:03Z] <RhinosF1> recreate deployment in py3.7 for T254246 END

Logs clear, nothing seems to have exploded.

I've ran multiple commands and checked the logs. So far, so good

22:32:26 <ZppixBot-test> RhinosF1: Sopel v7.0.4 (Python 3.7.3)

If this stays clear, I will deploy in ~36 hours to core.

Mentioned in SAL (#wikimedia-cloud) [2020-06-09T09:41:45Z] <RhinosF1> delete deployment to begin rolling back T254246 due to T254348

Mentioned in SAL (#wikimedia-cloud) [2020-06-09T09:47:14Z] <RhinosF1> rolled back sopelbot to python 3.5 -- END due to T254348 (cc T254246)

Rollback completed in ~8 mins for the record.

Mentioned in SAL (#wikimedia-cloud) [2020-06-24T15:46:23Z] <RhinosF1> updating test to py37 -- T254246

Will roll forward to master on Friday

Mentioned in SAL (#wikimedia-cloud) [2020-06-26T09:33:49Z] <RhinosF1> update python for bot (not cron) to py37 -- T254246

Mentioned in SAL (#wikimedia-cloud) [2020-06-26T09:45:46Z] <RhinosF1> update complete -- T254246