[00:01:14] <bd808>	 dwisehaupt: we can totally setup a redirect to prod via the process at https://wikitech.wikimedia.org/wiki/Nova_Resource:Redirects#Creating_a_new_redirect
[00:03:29] <bd808>	 dwisehaupt: the "File a bug report in Phabricator" link on that Nove Resource page is the easiest way to get it done. I can do all the needful things with puppet and horizon 
[00:07:08] <dwisehaupt>	 ok cool. 
[00:07:49] <dwisehaupt>	 we're trying to plan the transition phase now. i'm hoping i can just tell qgil and folks to use the new and we just shut off the old.
[00:08:05] <dwisehaupt>	 it's easy to force it, but i like to be nice. :)
[00:09:27] <dwisehaupt>	 thanks to both of you for being responsive.
[00:09:55] <bd808>	 dwisehaupt: as a user with an account on that CiviCRM instance I'm more than happy to help :)
[00:34:05] <wm-bb>	 <ALsatttt> سریع
[00:34:16] <wm-bb>	 <ALsatttt> Alo
[00:34:55] <wm-bb>	 <ALsatttt> www. Alo. Com
[00:35:11] <wm-bb>	 <ALsatttt> https://t.me/wmcloudirc/71529
[11:42:10] <mfossati>	 Hey folks, Marco here from the Structured Content team at WMF. Is it just me or the `toolforge` CLI is broken? I'm getting a `ModuleNotFoundError: No module named 'importlib.metadata'` when trying to execute from this tool: https://toolsadmin.wikimedia.org/tools/id/gogologo
[11:44:33] <arturo>	 mfossati: could you share which host are you running that from, and the complete command you are using?
[11:47:18] <mfossati>	 hostname is `tools-sgebastion-10` and the command is `toolforge`
[11:53:43] <wm-bb>	 <lucaswerkmeister> hm, is that the old buster bastion?
[11:53:57] <wm-bb>	 <lucaswerkmeister> when I SSH to toolforge(-dev) I get tools-bastion-12 or -13
[12:00:49] <mfossati>	 I'm using Marseille's `bast6003.wikimedia.org` as the bastion host
[12:05:19] <wm-bb>	 <lucaswerkmeister> which hostname are you connecting to?
[12:05:54] <wm-bb>	 <lucaswerkmeister> (the main Toolforge hosts are their own bastions – most tool developers don’t have access to the production bastions anyway ^^)
[12:05:59] <dcaro>	 looking
[12:06:35] <wm-bb>	 <lucaswerkmeister> ok, `login-buster.toolforge.org` sends me to tools-sgebastion-10, so apparently that’s still running and reachable
[12:06:39] <dcaro>	 mfossati: oh, you are running the toolforge clis directly on that bastion? (bast6003)
[12:07:15] <dcaro>	 ack
[12:07:40] <dcaro>	 mfossati: I can reproduce looking
[12:07:46] <mfossati>	 @dcaro bast6003.wikimedia.org is what I set in my SSH config 
[12:08:29] <mfossati>	 per https://wikitech.wikimedia.org/wiki/SRE/Production_access#Setting_up_your_SSH_config
[12:08:40] <dcaro>	 mfossati: should be fixed now
[12:08:44] <dcaro>	 can you try?
[12:08:57] <mfossati>	 wow that was fast
[12:09:04] <mfossati>	 lemme check
[12:09:21] <mfossati>	 it works!
[12:10:56] <wm-bb>	 <lucaswerkmeister> mfossati: FYI, those instructions are for production SSH access, you shouldn’t need any ProxyJump for toolforge (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Quickstart#Connect_to_Toolforge_servers_using_SSH)
[12:11:04] <wm-bb>	 <lucaswerkmeister> though I guess it doesn’t hurt very much either, other than adding a bit of latency to your connection
[12:11:20] <dcaro>	 ^ yep :), toolforge does not need to be accessed through prod bastions
[12:12:13] <mfossati>	 ok cool thanks a lot for the prompt support folks! <3
[12:12:46] <dcaro>	 👍
[12:12:52] <wm-bb>	 <lucaswerkmeister> also, if you’re connecting to `login-buster.toolforge.org`, I assume you’ll need to change that to `login.toolforge.org` sooner or later
[12:13:00] <wm-bb>	 <lucaswerkmeister> but I don’t know how long the old bastion will keep running :)
[12:13:53] <dcaro>	 not much, we will be removing it as soon as we can (trying to get alternatives for some flows that are not available/easy in the new bastions)
[12:14:08] <dcaro>	 so if you can use login.toolforge.org, I'd recommend using that instead
[12:15:40] <mfossati>	 indeed, I was using `login.tools.wmflabs.org`
[12:16:27] <wm-bb>	 <lucaswerkmeister> aah, okay
[12:16:49] <mfossati>	 too old I guess, haven't touched toolforge for a while
[12:28:17] <dhinus>	 should we maybe point login.tools to the new bastion? or maybe remove it completely?
[12:32:09] <wm-bb>	 <lucaswerkmeister> removing makes more sense IMHO
[12:32:26] <wm-bb>	 <lucaswerkmeister> tools-sgebastion-10 could maybe also use a hint in the login banner at this point?
[15:23:00] <bd808>	 login.tools.wmflabs.org has been "deprecated" since the toolforge.org domain introduction in 2020 -- https://wikitech.wikimedia.org/wiki/News/Toolforge.org
[15:28:54] * arturo has good memories
[15:31:08] <mfossati>	 \o/ been using it for so long :-D
[15:32:26] <wm-bb>	 <Mahima> Hello all,
[15:32:27] <wm-bb>	 <Mahima> I am experiencing an issue while trying to SSH into Toolforge. The error message I am encountering is as follows:
[15:32:28] <wm-bb>	 <Mahima> user@hostname ~ % ssh -i ~/.ssh/id_ed25519 username@login.toolforge.org
[15:32:30] <wm-bb>	 <Mahima> The authenticity of host 'login.toolforge.org (185.15.56.62)' can't be established.
[15:32:31] <wm-bb>	 <Mahima> ED25519 key fingerprint is SHA256:BD7PYn+h064QofXmhn69Ehos6skHvaki6MO+EOubL3Q.
[15:32:33] <wm-bb>	 <Mahima> This key is not known by any other names
[15:32:34] <wm-bb>	 <Mahima> Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
[15:32:36] <wm-bb>	 <Mahima> Warning: Permanently added 'login.toolforge.org' (ED25519) to the list of known hosts.
[15:32:37] <wm-bb>	 <Mahima> Connection closed by 185.15.56.62 port 22
[15:32:39] <wm-bb>	 <Mahima> If someone can help me sort it out, it would be a great help.
[15:34:41] <Southparkfan>	 !log deployment-prep starting kask maintenance - T370461
[15:34:44] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL
[15:34:45] <stashbot>	 T370461: Remove or replace deployment-sessionstore04.deployment-prep.eqiad1.wikimedia.cloud (Buster deprecation) - https://phabricator.wikimedia.org/T370461
[15:38:38] <bd808>	 @Mahima: what is your username?
[15:39:06] <wm-bb>	 <Mahima> agarwalmahima: UNIX Shell username
[15:40:11] <wm-bb>	 <Mahima> Wikimedia Developer Account : AgarwalMahima
[15:41:03] <bd808>	 @Mohima: I am not seeing Toolforge membership as an attribute of your Developer account. 
[15:41:33] <wm-bb>	 <Mahima> Yeah I have requested for Toolforge membership today itself.
[15:41:54] <bd808>	 you cannot access the servers until you are part of the project
[15:42:34] <wm-bb>	 <Mahima> Oh Okay that means i would be able to ssh into toolforge once my membership request is accepted.
[15:42:57] <bd808>	 yes
[15:43:13] <wm-bb>	 <Mahima> Thankyou.
[16:18:29] <andrewbogott>	 Mahima, you're approved now :)
[16:18:55] <wm-bb>	 <Mahima> Thankyou :)
[16:21:37] <wm-bb>	 <Mahima> Yeah now i can ssh into toolforge :)
[16:26:19] <wm-bb>	 <Mahima> But the approval is not reflecting on my Wikimedia Tools admin portal.
[16:29:32] <wm-bb>	 <Mahima> Yeah it is reflecting now thanks
[16:55:49] <Southparkfan>	 !log deployment-prep cancel kask maintenance, not going to perform switchover yet, see https://phabricator.wikimedia.org/T370461
[16:55:57] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL
[17:15:42] <wm-bot>	 !log dcaro@tools-bastion-13 tools.api-docs deployed changes using toolforge cdn
[17:15:44] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.api-docs/SAL