[10:53:13] <dhinus>	 !log tools.templatetransclusioncheck restarted stuck pod T346126
[10:53:17] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.templatetransclusioncheck/SAL
[10:53:17] <stashbot>	 T346126: Some of my tools (eg wikidata-todo) just start throwing 504 errors - https://phabricator.wikimedia.org/T346126
[12:33:04] <Rook>	 !log paws jupyterlab to 4.0.9 T351726
[12:33:08] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL
[12:33:09] <stashbot>	 T351726: jupyterlab to 4.0.9 - https://phabricator.wikimedia.org/T351726
[14:46:06] <andrewbogott>	 !log tools shuffling toolforge etcd nodes all over the place in order to reimage cloudvirtlocal hosts
[14:46:09] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[15:23:20] <andrewbogott>	 audiodude, i'd like to delete the 'test-postgres' database instance in the 'quarry' project. Is that yours?
[20:42:34] <bd808_>	 TFW a bug is caused by someone's bot still using a hostname scheme for connecting to the Wiki Replicas that was deprecated in 2017. :(
[20:43:55] <bd808_>	 I wonder if we should break all the `*.labsdb` using things at the same time now that they are double legacy (or triple?)
[20:48:06] <bd808_>	 context: in T351316 we learn that srwiki once was in s3, but now is in s5. srwiki.labsdb still points to s3 because the *.labsdb hostnames which became legacy in 2017 are static data since T260389 in 2020.
[20:48:07] <stashbot>	 T351316: 'mbh' tool cannot log in to srwiki's DB replica when attempting to connect using the legacy 'srwiki.labsdb' hostname - https://phabricator.wikimedia.org/T351316
[20:48:07] <stashbot>	 T260389: Redesign and rebuild the wikireplicas service using a multi-instance architecture - https://phabricator.wikimedia.org/T260389