[10:17:36] !log redirects Add petscan.wmcloud.org to redirect to equivalent Toolforge service T442887 [10:17:39] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Redirects/SAL [10:17:40] T442887: Retire petscan.wmcloud.org and forward to petscan.toolforge.org - https://phabricator.wikimedia.org/T442887 [10:34:38] Hi, I am having an issue attaching a cinder volume to a VPS. As per the instructions (https://wikitech.wikimedia.org/wiki/Help:Adding_disk_space_to_Cloud_VPS_instances): [10:34:39] ``` [10:34:40] $ sudo wmcs-prepare-cinder-volume [10:34:42] This tool will partition, format, and mount a block storage device. [10:34:43] Attached storage devices: [10:34:45] sda: (the primary volume containing /) [10:34:46] sdb: new volume, will be formatted before mounting [10:34:48] The only block device device available to mount is sdb. Selecting. [10:34:49] Where would you like to mount it? /data [10:34:51] Ready to prepare and mount sdb on /data. OK to continue? Y [10:34:52] Formatting as ext4... [10:34:54] mke2fs 1.47.2 (1-Jan-2025) [10:34:55] Discarding device blocks: 50331648/78643200``` [10:34:57] It has been going on like this for at least 30 minutes with the number of discarded block slowly rising. [10:34:58] Am I correct in assuming there is some problem with that volume? [10:44:44] @CristianCantoro hmm it's usually faster, but the "discarding" message is not necessarily an issue. how big is the volume? [10:50:24] !log admin put back cloudvirt1050 in service [10:50:29] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [10:55:57] it completed correctly, the volume is 300GB (re @wmtelegram_bot: @CristianCantoro hmm it's usually faster, but the "discarding" message is not necessarily an issue. how big is the volu...) [14:12:50] Hi, when I'm added as a maintainer for a tool on tooladmin, should I expect to automatically receive git repo write access on gitlab? I found there's a separate ACL for the repo owners. https://toolsadmin.wikimedia.org/tools/id/wsstats https://gitlab.wikimedia.org/toolforge-repos/wsstats [14:13:42] i believe the acl is currently only automatically synced when the tool is first created and any later changes in maintainer access will need to be done manually [16:32:10] Thanks, i'm asking the current maintainer to grant me the access. Would it make sense to make StrikerBot do this automatically? [16:35:58] I think it would usually make sense (we want to encourage maintainers to use git and to commit and publish their changes, especially when the buildservice is involved) but some projects may have a reason that I can't think of [16:37:07] Hi, is toolforge-repos/sample-complex-app-frontend / toolforge-repos/sample-complex-app-backend actually maintained? Or do we have another PTD (regularly deployed) example repo? Looking for something where the image is almost guaranteed to exist (without relying on my own components). That image comes back with a bunch of vulns including the brotli/node2shell (node 24.15.0) and it is running currently. [16:41:15] Damianz: I would say yes, not as an official policy but we are still using those repos to test new toolforge features [16:41:53] Great - I'll make a ticket re bumping the deps up, not super urgent just was surprised it came back with a load [16:42:17] thanks! [16:42:49] we do have in our backlog to look more carefully at the brotli impact on toolforge tools, but E_TOO_MANY_SEC_VULNERABILITIES :) [16:44:57] in theory a fresh build of a Node tool should not be vulnerable though, I will trigger a build for both toolforge-repos/sample-complex-app-frontend and toolforge-repos/sample-complex-app-backend [16:45:21] see also https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.org/thread/TCUZGJX6H4OYZKOIPNVNKB63LIPGQFG6/ [16:48:20] The slightly odd thing is it had a recent build, which should be using the recent builder that supports the fixed node version (I don't have access to the build logs just https://gitlab.wikimedia.org/toolforge-repos/sample-complex-app-backend/-/pipelines/243035 but apparently it didn't get the latest [16:49:02] I assume there is a pin somewhere in the repo, but I'm still resisting dealing with npm, despite everything seeming to need it these days :) [16:50:45] I didn't see a recent build though, only a recent deployment that reused an old build (if I'm not mistaken) [16:51:15] so redeploying is not enough, I had to run "toolforge components deployment create --force-build", now it should be fixed. can you double check? [16:52:40] Ah yes, that would make sense... I was kind of assuming it had done a build while builds-api was returning nonsense the other day, but didn't explicitly check. Let me see what it looks like now [17:00:39] Yeah it got node 24.22.1 now and the list went down a bunch thanks [17:02:17] thank you for spotting this! [17:03:18] It was purely by chance while moving to syft + trivy rather than just trivy for my own stuff, which is a lot better at finding buildpack things [18:11:47] @PhV6OSm4va3IiJ, taavi: T317376 exists for syncing gitlab and toolsadmin fwiw [18:21:37] dologmsg tools.quickcategories deployed ce128c0c4a..f8e2eee8bc: Delete old OAuth credentials from database (and Quote @monthly syntax in toolforge.yaml *sigh*) [18:25:15] derp [18:25:20] !log tools.quickcategories deployed ce128c0c4a..f8e2eee8bc: Delete old OAuth credentials from database (and Quote @monthly syntax in toolforge.yaml *sigh*) [18:25:22] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.quickcategories/SAL [18:25:25] thanks stashbot [18:33:00] also, for anyone who’s interested in such things, the QuickCategories toolforge.yaml file now has an example of a webservice, a continuous job, and a scheduled job https://gitlab.wikimedia.org/toolforge-repos/quickcategories/-/blob/f8e2eee8bc/toolforge.yaml, which I guess are the three major kinds of components you might find there [18:33:40] (I believe once T362077 is done, the webservice will actually be its own type and not just a slightly differently configured continuous job ^^) [18:33:41] T362077: [components-api] Add webservice support - https://phabricator.wikimedia.org/T362077 [19:25:08] Nice you are using reuse_from [21:47:27] yup, no need to build the same image three times :D [22:05:47] someone remind me which tools i run include an irc bot component [22:10:26] I don’t know enough about which tools you run 😔 [22:10:32] ircservserv [22:10:44] just glancing through https://ldap.toolforge.org/user/taavi, bridgebot, irc-wmt, ircservserv, maybe stewardbots? [22:11:04] i think this is a sign that i maybe have a bit too many tools that i am somehow involved with [22:11:16] clearly we need more tool directories to answer questions like this [22:11:19] the heck is irc-wmt [22:11:45] wait does ldap show tools recursively now? [22:13:10] yes [22:13:15] hm, looks like it https://ldap.toolforge.org/group/tools.irc-wmt [22:13:19] via stewardbots I guess? [22:13:31] must be [22:19:28] i don't know what it is easier, before my time [22:20:21] You are not a member of the group tools.irc-wmt. [22:20:33] huh, https://ldap.toolforge.org/user/anticomposite says I am as well. [22:21:02] need to become stewardbots first? [22:21:25] yeah that works [22:26:05] looks like irc-wmt was doing *something* with a php5 container until recently [22:50:13] apparently index.php is just a placeholder [22:51:08] there's a bunch of references to freenode.net and 0 to libera.chat so I think it's good and dead [22:54:20] !log tools.irc-wmt webservice stop - was a php5 container, and index.php just contains a placeholder. This tool is apparently an IRC thing, but only references freenode. It seems dead. [22:54:22] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.irc-wmt/SAL