[01:14:59] Watch live stream Daily Chat... on binance live https://www.binance.com/en/live/video?roomId=2146698&utm_campaign=binance_live [08:18:56] !log puppet-dev prune old reports from pm7:/var/lib/puppetserver/reports to free up disk space [08:18:58] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Puppet-dev/SAL [09:25:01] hi folks, when you get a chance I could use some assistance on https://phabricator.wikimedia.org/T343039 re: clouddb [09:25:31] taavi: sorry I haven't found the time to go ahead with the graphite reviews [09:25:49] no worries [09:27:14] godog: looking at that task it's quite unclear what they're trying to do. normally if you were to just connect to the replicas you'd log in to a toolforge bastion or a stat* box and connect from there using a script, but I'm not sure if that's what they actually want to do? [09:27:54] taavi: mmhh maybe stat boxes is what they are after [14:51:30] do y'all do any customize of your VM images, or do you just use the debian cloud image? [14:57:08] the base images on cloudvps are a little bit customized to add the puppet stuff, and ldap mostly, is that what you are asking about? [14:57:51] details here: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/VM_images [15:01:37] dcaro yeah, looking at what it would take to use vm images in ganeti and wanted to see how y'all did image builds [17:03:27] inflatador: iirc vanilla upstream images + cloudinit work fine in our deployment. We prebuild images so that users don't have to wait for the extremely slow initial puppet run. [17:04:47] So the things you'll need are: 1) port mapping for cloud-init, 2) a dns alias for puppet 3) some way of auto-signing puppet certs. [17:04:48] that might be it [17:05:15] I can tell you more about autosigning if you get that far, it is not at all complicated. [17:06:26] * andrewbogott has to run an errand, back later [17:11:23] andrewbogott no worries, I'm just putting together a proof of concept for Infra Foundations to review. Would probably use nocloud for cloud-init as opposed to metadata service [17:18:52] Toolsadmin has notifications now! Fancy [17:19:10] I appreciate having a visible audit log of all the different state changes I’ve made over the last several years [19:26:53] Hi. My name is Jorge. My username is Pepe piton. I am new to toolforge and wikimedia gitlab accounts. I have an account and a tool on toolforge and an authrised account on gitlab. But when I go to "Create new GitLab repository" in my tool account, I receive an error message which says "No GitLab accounts found for tool maintainers." I have double checked that I am listed as a mai [19:26:53] nteiner of the tool. I'd appreciate receiving some guidance to create the repository. Thank you very much! [19:31:17] @Jorgemet: I can look for error logs that might better explain the problem. Was this for your "paulina" tool? [19:32:23] * bd808 found a related error in logstash [19:34:10] "Failed to lookup user 'pepepiton'" -- I'll poke around a bit more to see if I can understand why https://gitlab.wikimedia.org/pepepiton was not located by my code. [19:38:11] yes, it is for paulina tool. (re @wmtelegram_bot: @Jorgemet: I can look for error logs that might better explain the problem. Was this for your "paulina" tool?) [19:39:24] I can access my gitlab account at https://gitlab.wikimedia.org/pepepiton [19:39:48] @jorgemet: I have created T343485 to track your issue [19:39:49] T343485: "No GitLab accounts found for tool maintainers." failure when attempting to create GitLab repo for paulina tool - https://phabricator.wikimedia.org/T343485 [19:40:17] thank you very much! [19:43:04] where was striker code? [19:47:40] Platonides: https://gerrit.wikimedia.org/g/labs/striker [19:50:05] I have a hunch what the problem may be. There was a change in the auth provider for GitLab recently and no related config change for Striker. [19:54:06] looks promising [19:54:47] ugh. yup. the issue is actually that the "identifier" for the external auth service has changed from being the Developer account shell name under CAS to the Developer account user name under ODIC. This is related to recent changes for T320390 [19:54:47] T320390: migrate gitlab away from the CAS protocol - https://phabricator.wikimedia.org/T320390 [19:56:21] * bd808 wonders how to fix this... [19:56:27] it's odd that it raised an IndexError, when there is a try: except: that should have catched it [19:57:14] Platonides: the log message is output by logger.exception() so that part is jsut showing what triggered the catch [19:57:48] oh, if that was by logger.exception then it makes sense [20:00:42] In case it may be of any help, my developer account username has a space in between (Pepe piton), but the Phabricator account has an underscore (Pepe_piton) because it didn't accept spaces. [20:07:04] @Jorgemet: The issue appears to be unrelated to you or your tool. Instead there has been a needed configuration change in GitLab that Striker has not yet been updated to work with. [20:07:19] and the uid has no space :p [20:09:42] Oh, thank you, I am glad I helped identifying a bug. Thank you! [20:13:30] @Jorgemet: This is going to take me a while to fix properly, but I can do some sneaky things to get your repo created in advance of that. [20:14:34] Thank you, I would really appreciate it. [20:15:47] @Jorgemet: https://gitlab.wikimedia.org/toolforge-repos/paulina [20:17:04] Thank you very much!