[11:31:44] !log toolsbeta aborrero@toolsbeta-test-k8s-control-4:~$ sudo -i kubectl apply -f /etc/kubernetes/toolforge-tool-roles.yaml (https://gerrit.wikimedia.org/r/c/operations/puppet/+/889836) [11:31:49] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [11:32:43] !log tolls aborrero@tools-k8s-control-2:~$ sudo -i kubectl apply -f /etc/kubernetes/toolforge-tool-roles.yaml (https://gerrit.wikimedia.org/r/c/operations/puppet/+/889836) [11:32:43] arturo: Unknown project "tolls" [11:32:50] !log tools aborrero@tools-k8s-control-2:~$ sudo -i kubectl apply -f /etc/kubernetes/toolforge-tool-roles.yaml (https://gerrit.wikimedia.org/r/c/operations/puppet/+/889836) [11:32:53] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [13:21:43] getting `Error: /Stage[main]/Base::Remote_syslog/Puppet::Expose_agent_certs[/etc/rsyslog]/File[/etc/rsyslog/ssl/cert.pem]: Could not evaluate: [...]` when running `sudo puppet agent -tv` on a couple of `commtech` WMCS VPSs — known issue? [13:24:37] output at https://phabricator.wikimedia.org/P44917 [16:05:23] TheresNoTime: I wonder if it has something to do with that hostname being in title case... [16:06:19] I was hoping y'all would say "oh yeah that's everyone don't worry about it" [16:07:44] Maybe the puppetmaster has more info on why it could not fetch the files [16:08:06] !log commtech Fixed puppet run on commtech-Wiki-002.commtech.eqiad1.wikimedia.cloud by editing /etc/hosts to make hostname all lower case [16:08:10] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Commtech/SAL [16:08:11] it was the title case [16:08:27] TheresNoTime: don't name your hosts with title case names :) [16:08:33] 🙃 thank you bd808 [16:08:40] It wasn't me!! :p [16:09:01] there's probably a bug to file here against Horizon for allowing that [16:09:04] Oh that one might have been... But I was copying 001.. oop [16:11:15] !log commtech Fixed puppet run on commtech-wiki-001.commtech.eqiad1.wikimedia.cloud by editing /etc/hosts to make hostname all lower case [16:11:18] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Commtech/SAL [16:40:50] Hello. [16:42:12] I liked to host my Flask tool that uses pycurl. However, it says that curl-config is not found. [16:42:20] What should I do. [16:53:57] @Csisc1994: my first suggestion would be to use a pure Python lib like Request instead. If that is not possible, you can file a task under https://phabricator.wikimedia.org/project/view/3978/ asking for the library to be added to the Python container images. That doesn't guarantee it will happen, but it can start a discussion. [16:55:44] The problem is that the Library that uses PyCurl is WPTools and I need it to let my tool work. (re @wmtelegram_bot: @Csisc1994: my first suggestion would be to use a pure Python lib like Request instead. If that is not possible, you can...) [16:58:30] @Csisc1994: *nod* You could also look for another MediaWiki API library such as pywikibot or mwclient, but I understand if that is not possible or desired for you. [16:59:38] Do they extract the lead of a Wikipedia article. (re @wmtelegram_bot: @Csisc1994: *nod* You could also look for another MediaWiki API library such as pywikibot or mwclient, but I understand ...) [17:00:55] @Csisc1994: the trunk of wptools seems to have dropped the pycurl requirement. It looks like there has not been a new versioned release of the library in nearly 5 years however. [17:05:00] It worked on my laptop. Can I get rid of the PyCurl requirement. (re @wmtelegram_bot: @Csisc1994: the trunk of wptools seems to have dropped the pycurl requirement. It looks like there has not been a new ve...) [17:33:47] Can you troubleshoot Sawtpedia to see why it does not currently work. [17:41:26] @Csisc1994: "No module named 'flask'" in $HOME/uwsgi.log. Sounds like a problem with your $HOME/www/pything/venv [17:44:41] It is installed. (re @wmtelegram_bot: @Csisc1994: "No module named 'flask'" in $HOME/uwsgi.log. Sounds like a problem with your $HOME/www/pything/venv) [17:46:17] I did not figure out why this occurred. [17:48:48] @Csisc1994: your venv was built with Python 3.7 and your webservice is trying to run with Python 3.9. This does not work. You need to either rebuild the venv using Python 3.9 or downgrade your container version to 3.7. [17:49:11] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web/Python#Creating_a_virtual_environment [17:50:16] Running `webservice-python-bootstrap --fresh` from inside a `webservice python3.9 shell` session and then exit to the bastion and rung `webservice restart` should fix things up. [17:50:46] oh, but that assumed you had a requirements.txt and you don't [17:51:25] so the same thing, but you have to use manual steps to delete the existing venv and create a new on with your needed libraries in it [18:03:53] I see. [18:03:58] Thank you.