[09:16:32] <arturo>	 !log tools upgrading k8s cluster to 1.22 (T286856)
[09:16:38] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[09:16:38] <stashbot>	 T286856: Upgrade Toolforge Kubernetes to latest 1.22 - https://phabricator.wikimedia.org/T286856
[10:46:38] <taavi>	 !log tools patch existing PSP roles to use policy/v1beta1 T331619
[10:46:42] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[10:46:43] <stashbot>	 T331619: toolforge: rbac: change existing roles to reference PSP in the policy group - https://phabricator.wikimedia.org/T331619
[12:39:59] <Rook>	 !log paws openrefine version bump 771250537d42d16bed997c3bd1f7f500512e634b T334145
[12:40:04] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL
[12:40:04] <stashbot>	 T334145: New version of OpenRefine  - https://phabricator.wikimedia.org/T334145
[13:58:13] <wm-bb>	 <harej> I have a web service I want to run on Toolforge. It comes with a `run-api.sh` file that only consists of this command: ```
[13:58:13] <wm-bb>	 <harej> gunicorn -w 4 wsgi:app```
[13:58:15] <wm-bb>	 <harej> . How does this map to Toolforge webservice concepts?
[14:06:34] <taavi>	 harej: the closest match is the python3.x webservice types on kubernetes. you will need to move wsgi.py to app.py, but otherwise it should work out of the box. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web/Python
[14:27:32] <wm-bb>	 <harej> https://check-references.toolforge.org/ I am getting 503 Service Temporarily Available. I am not getting useful errors in `uwsgi.log`; I did get an error before, about a dependency being installed, but now that dependency is installed and I am getting that error with no additional feedback.
[14:30:25] <wm-bb>	 <lucaswerkmeister> how did you install the dependency? I don’t see a www/python/venv in that tool
[14:31:00] <wm-bb>	 <harej> `become check-references` then `source venv/bin/activate` then pip
[14:31:18] <wm-bb>	 <lucaswerkmeister> oh, the venv/ is directly in the tool’s home directory
[14:31:29] <wm-bb>	 <lucaswerkmeister> the webservice isn’t going to use that, it should be in www/python/venv/
[14:31:52] <wm-bb>	 <lucaswerkmeister> you should recreate it there (moving the existing one probably won’t work, venvs aren’t location-independent)
[14:40:03] <roy649>	 Also, you can't build the venv on the toolforge bastion; you need to connect to a pod and build it there.
[14:40:08] <roy649>	 webservice --backend=kubernetes python3.9  shell
[14:40:37] <roy649>	 If you build your venv on the bastion host, it'll mostly work, but you'll be chasing bizarre errors forever.
[14:40:55] <roy649>	 The problem is that some pathnames that get embedded in the venv are different on the bastion and the pod.
[14:41:22] <wm-bb>	 <lucaswerkmeister> right, good point, on the bastion you would also get python 3.7 instead of 3.9
[14:43:22] <roy649>	 It's more than just 3.7 vs 3.9; some of the nfs paths to home directories are different.  I forget the details, but "just always do venvs on the pod" is a rule that works.
[17:51:17] <wm-bot>	 !log tools.lexeme-forms <lucaswerkmeister> deployed 282a7b6b18 (l10n updates: anp; currently skipped because unsupported by Babel)
[17:51:20] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL