[14:57:19] Hi Cloud Services team, I tried to SSH to the beta cluster, but I didn't seem to be able to connect. When running in verbose mode, it shows me the logs below. Anyone have similar problems? Thanks. [14:57:19] debug3: send packet: type 50 [14:57:20] Connection closed by "IP::PORT" port 22 [14:57:20] kex_exchange_identification: Connection closed by remote host [15:03:21] seanleong-wmde: can you paste the full -v output on a pastebin and link the output here? [17:57:46] I'm seeing DB overload errors on various wikis today — is everything expected? [17:57:47] """Sorry! This site is experiencing technical difficulties. [17:57:48] Try waiting a few minutes and refreshing. [17:57:50] (Cannot access the database: Cannot access the database: Database servers in cluster31 are overloaded. In order to protect application servers, the circuit breaking to databases of this section have been activated. Please try again a few seconds.)""" [17:58:04] https://www.wikimediastatus.net/ [18:27:45] !log lucaswerkmeister@tools-bastion-15 tools.speedpatrolling deployed f1b263f216 (upgrade dependencies) and 32a27cf571 (fix README) [18:27:48] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.speedpatrolling/SAL [18:53:49] !log lucaswerkmeister@tools-bastion-15 tools.speedpatrolling deployed 77c45c428a (Python 3.14) [18:53:52] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.speedpatrolling/SAL [19:11:02] !log lucaswerkmeister@tools-bastion-15 tools.speedpatrolling deployed fa3fbc988f (Toolforge Components Service, push-to-deploy) [19:11:05] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.speedpatrolling/SAL [19:23:02] random bit of feedback about the new components service: I don’t like the CLI very much ^^ [19:23:03] the “entrypoint” subcommand is `toolforge components`, which IMHO is just not that relevant. 99% of my tools will have exactly one component, and even in the one tool that has more components (QuickCategories, with a background runner), that’s hardly the most important quality of the tool [19:23:05] also I find it annoying that `toolforge components d[TAB]` only tab-completes up to `deploy`, at which point it’s ambiguous between `deploy-token` (I will generally use this exactly once ever) and `deployment` (much more useful – even with push-to-deploy I’ll want to `list`/`show` deployments from time to time) [19:23:06] suggestion: rearrange the CLI around the `deployment`, like so: [19:23:08] `toolforge deployment list/show/…` [19:23:09] `toolforge deployment config create/show/…` [19:23:11] `toolforge deployment token create/…` [19:24:21] (although now that I type that out, it’s awkward how `toolforge deployment show` and `toolforge deployment config show` have a different number of “levels”… this sounded better in my head. meh. but still, that’s my feedback, you can do what you want with it ^^) [19:28:48] lucaswerkmeister: feedback is useful! But a phab task might be more persistent [19:29:18] this one felt too unsubstantial for a task 😅 (I also filed https://phabricator.wikimedia.org/T439030 earlier) [19:29:24] but I guess I can create another task if you prefer [21:14:56] up to you but it might be forgotten if it doesn't make it to phab. [21:46:52] !log deployment-prep cherry-pick https://gerrit.wikimedia.org/r/c/operations/puppet/+/1344336 to Puppetserver - T435393 [21:46:58] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL [21:46:58] T435393: Beta Cluster: Switch to PHP 8.5, includes writing Puppet changes to support PHP 8.5 on baremetal - https://phabricator.wikimedia.org/T435393