[00:35:38] Mmmmm IRC [09:12:46] !log clouddb-services disabled puppet checks on clouddb100[3-4] (touch /.no-puppet-checks) T323159 [09:12:49] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Clouddb-services/SAL [09:12:49] T323159: Shut down osmdb.eqiad.wmnet (clouddb100[3-4])? - https://phabricator.wikimedia.org/T323159 [14:18:57] Hm. nemobis@tools-sgebastion-10:~$ kubectl get pods [14:18:57] The connection to the server localhost:8080 was refused - did you specify the right host or port? [14:19:24] Nemo_bis: you need to `become` a tool first [14:19:42] lol right [14:21:29] trying to fix python2 compatibility issues is making me unlearn things I knew only few hours ago, I should probably stop [14:22:28] I love them days [14:24:41] Isn't the answer to python2 compatibility issues "just say no" at this point? [14:25:04] definitely [14:26:08] but I discovered one long-broken python2 tool works just fine on tools-sgebastion-10 (Debian 10 with python2) and I thought, how hard could it possibly be to make it also work again on the kubernetes jobs? [14:28:28] Given that py-2 hasn't even gotten security fixes in years, it shouldn't even be allowed on WMF machines any more. [14:46:23] does that really affect this tool? [14:47:05] what seurity issues are wontfixed in last python2? [14:47:38] I can only think on it not verifying certificates by efault but i think it might have been done in a 2.x branch, not only on py2 [14:52:43] The issue isn't that there's things that weren't fixed. The issue is the future exposure. What happens when there's some new, critical, "get root in 10 seconds on any machine" exploit that comes out and the py-dev folks say, "Sorry, not our problem; we told you not to keep running this". [14:55:04] "what happens" <-- if the issue is bad enough, we pull the python2 images from the registry, easy peasy [22:10:00] !log admin upgrading codfw1dev openstack to version 'zed' [22:10:03] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL