[06:30:21] is there some known issue with the bot which adds reviewers in Gerrit? normally Simon and myself are auto-added as reviewers for anything which modules/admin/data/data.yaml, but that didn't happen for https://gerrit.wikimedia.org/r/c/operations/puppet/+/1352166 and https://gerrit.wikimedia.org/r/c/operations/puppet/+/1352258 [07:07:35] as FYI I am going to rollout the latest external-services configs in all k8s clusters, to pick up the new PKI LVS IPs.. [07:40:56] all k8s clusters using pki.discovery now [11:40:39] heads-up, I am about to merge a change to remove a bunch of graphite config. might make for some noise but will mostly only affect graphite and things misconfigured to keep using it [11:48:21] graphite hosts are now insetup, RIP [11:56:27] 🎉 [12:06:28] the change broke puppet on cp hosts :( reverting [12:20:14] correction: no need for a revert, all is well [12:28:13] <_joe_> hnowlan: you monster, you deleted some important metric history! [12:28:45] <_joe_> you're like the people pouring cement on Rome's empire remains just to build a metro line! [12:28:50] <_joe_> (congrats) [13:11:10] moritzm: hmmm https://gerrit-reviewer-bot.toolforge.org/ [13:13:27] not listed on the service catalog either [13:44:40] as FYI I moved bare-metal-prod back to pki.discovery.wmnet [13:44:51] so now we don't use the host-specific settings anymore [13:51:00] excellent! [13:51:28] hashar: ^ do you happen to know who runs gerrit-reviewer-bot [13:52:28] moritzm: unowned afaik [13:53:51] I guess valhallasw (a volunteer) is the de factor maintainer. The code is at https://github.com/valhallasw/gerrit-reviewer-bot [13:57:06] anyway if there is an issue with it, that can be filed in Phabricator against `#gerrit`  and we/I will cc valhallasw on it [13:57:20] I don't think I am even a member of that tool [15:28:56] JennH: did you reboot db2201 or did it crash again? [15:29:20] oh sorry that was me. i forgot to check if it was downtimed. my bad [15:29:26] i'm upgrading the bios [15:29:39] yeah, I wanted to stop mariadb too first, but no worries [15:29:45] let me know when it is up again [15:30:16] it looks like it's up now. very sorry [15:31:08] JennH: no worries, did you get the tsr report too? [15:31:30] not yet. i have a few more firmware updates to do. then running the tsr [15:31:40] ah ok, will that imply a reboot? [15:31:46] double checking [15:32:12] yes [15:32:18] I've downtimed it now, just asking to see if I can start mariadb or rather wait till you are fully done [15:32:29] JennH: ok, then I will wait, can you post in the task once you are fully done? [15:32:46] will do [15:32:50] thank you! [19:40:20] is it okay for me to do the first deploy of a chart to production on my own (editcheck-headless, which has been trialed in staging for a while), or do you prefer someone SRE-related to be keeping an eye on that? [19:41:30] Actually, I should probably ask that more specifically in -serviceops [19:53:24] For T440334, is the production-image build log viewable for mortals like me so I can self-diagnose? [19:53:24] T440334: abstractwiki-rust 1.94.1-3-20261004 didn't get published in the weekly re-build, did the build fail? - https://phabricator.wikimedia.org/T440334 [19:57:09] Aha, it looks like it’ll be on build2004.codfw.wmnet to which I can’t shell. Ah well. [21:26:30] James_F: there's a rust compile error, I'll paste the log to the task [21:29:55] Thanks. [21:30:41] https://phabricator.wikimedia.org/T440334#12409143 [21:31:44] we should also eventually handle errors better, by e.g. auto-creating Phab tasks (but needs some groundworks before that can happen, like better meta data)