[10:23:06] <wm-bb>	 <dpriskorn> I'm having trouble using pip in Kubernetes in the image: python3.11.
[10:23:07] <wm-bb>	 <dpriskorn> Neither pip nor pip3 exists.
[10:23:08] <wm-bb>	 <dpriskorn> code here https://github.com/dpriskorn/DiVAScraper/blob/master/run-job.sh
[10:23:10] <wm-bb>	 <dpriskorn> If anyone knows how to make it work or point me to relevant documentation for the images I would be very happy :)
[13:37:33] <wm-bb>	 <Yetkin> Toolforge-jobs kills my job. Why? I cannot see any details in the .err file
[13:50:38] <wm-bb>	 <Yetkin> @albertoleoncio
[14:42:24] <wm-bb>	 <bd808> Often this means that the job is running out of ram (re @Yetkin: Toolforge-jobs kills my job. Why? I cannot see any details in the .err file)
[14:43:45] <wm-bb>	 <Yetkin> It would be good to have a more detailed report as to why the job fails. Should I make a request on Pahbricator?
[14:46:02] <wm-bb>	 <bd808> You need to use a venv. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Python#Virtual_environments (re @dpriskorn: I'm having trouble using pip in Kubernetes in the image: python3.11.
[14:46:02] <wm-bb>	 <bd808> Neither pip nor pip3 exists.
[14:46:04] <wm-bb>	 <bd808> code here https://github.com/d...)
[14:49:58] <wm-bb>	 <bd808> https://phabricator.wikimedia.org/T306310 might be what you are hoping for. (re @Yetkin: It would be good to have a more detailed report as to why the job fails. Should I make a request on Pahbricator?)
[15:17:29] <wm-bb>	 <Yetkin> Thanks for the ticket reference. How can I troubleshoot the issue I am having? The same job has run successfully many times on the Grid Engine
[15:33:49] <wm-bb>	 <bd808> Yetkin Kubernetes is much better/more strict at enforcing ram and cpu limits than grid engine is. I would suggest running your job with more ram to see if that solves your problem. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Jobs_framework#Job_quotas
[15:35:29] <wm-bb>	 <Yetkin> will try...
[17:56:09] <paladox>	 Hi, it looks like wiki bugs needs restarting as it seems to have stopped reporting.
[19:25:09] <wm-bb>	 <Yonatan> Hi, seems like the glams dashboard DB is down again. Instead lf troubling you guys I thought I'd follow the DIY troubleshooting described in phabricator T355138. However, neither I or the project admin that I've talked to have access to the puppet repo to get the SSH keys necessary to access the VM. I was wondering how can I get that access/who should i talk to
[20:57:47] <andrewbogott>	 !log admin running wmcs.openstack.restart_openstack for all eqiad1 services
[20:57:51] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL
[20:58:36] <andrewbogott>	 Yonatan, can you tell me more about how the project admin and puppet access?  ssh keys are provisioned by ldap, if they're a project admin they should have acess
[20:59:06] <andrewbogott>	 oh, I see, it's that broken trove VM... I'll take a look