[10:06:19] dhinus: it seems that the versioning issue is because we use helmfile apply, not helmfile sync, apply will only run sync if there's a diff [10:07:26] https://helmfile.readthedocs.io/en/latest/#apply [10:12:28] ah nice! [10:13:16] I will try manually using sync on toolsbeta to see if that fixes it [10:18:08] 👍 [10:18:32] note that it might require some secrets and such that are handled by the script before running helmfile I think [10:29:05] dhinus, dcaro I just sent a calendar invite for 30m from now, I would like to show you how the tofu-infra refactor is going before continuing with my work [10:29:42] thanks, the time works for me [10:29:47] thanks! [10:34:25] quick review (enable qos config in eqiad) https://gerrit.wikimedia.org/r/c/operations/puppet/+/1126618/1 [10:36:05] +1 [10:37:46] thanks! [11:31:19] 👋 I'm trying to check the logs of a web tool (schedule-deployment) as per https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web#View_web_service_logs but I can't `become` because I'm not in the project [11:31:44] do I need to be added to the project to see the logs or is there any other way? [11:35:28] jnuche: yes, you need to be added to the project, by a current tool member [11:35:32] yep, you have to be added to the project yes [11:36:10] the maintainers are listed here: https://toolsadmin.wikimedia.org/tools/id/schedule-deployment [11:36:23] alright then, ty! [11:37:55] jnuche: do you have a toolforge account? if so, maybe I can add you to the list, and bd808 can revert later if he doesn't agree with you being on the list [11:38:41] ah, that'd be awesome, account is "Jaime Nuche" [11:39:33] I can see myself already in the list of maintainers [11:39:39] thanks a lot arturo :) [11:39:54] you are welcome [12:56:38] arturo: does toolforge requires another account than the Wikitech one? [12:56:51] * hashar suddenly realizes there is no more such thing as a Wikitech account [12:57:01] or LDAP :b [12:57:02] hashar: no, it requires your developer account to be "accepted" in toolforge [12:57:15] AH "developer account", that is the semantic I was looking for :) [12:57:24] thx! [12:58:48] yeah, I wasn't exactly sharp when I selected my words, but we could understand each other [14:27:56] arturo: na your were perfect, we just have too many semantics :) [16:32:22] dcaro: Raymond_Ndibe I'm sorry I wont make it to the components-api meeting, I'll catch up at other time [16:38:43] ok I found the problem with helmfile: I have to run it from a control node, not from the bastion! [16:41:56] dhinus: sounds right [16:42:27] arturo: 👍 [16:43:09] I managed to upgrade the components using "helmfile sync" in deploy.sh, the only issue is that while apply asks for confirmation, sync does not (I think) [16:44:13] well I'm confused because the help page says the --interactive option is valid for sync [16:48:45] LOL I'm not the only one confused: https://github.com/helmfile/helmfile/issues/324 [16:52:38] that was fixed in helmfile v0.145.5 and we are running v0.144 ROTFL [17:10:27] we forked a WMCS version T339328 but now production has a newer version than us [17:10:28] T339328: [helmfile] Toolforge needs helmfile >=/0.145.3, but we have 0.135.0 - https://phabricator.wikimedia.org/T339328 [17:41:28] verified that upgrading helmfile, deploy.sh now asks for confirmation! [17:56:08] I deleted our version from the toolforge APT repo, so we're pulling the prod one from apt.wikimedia.org [18:29:17] nice! [18:29:19] * dcaro off [22:10:53] a.rturo: I finally read that blog post on nftables & kube-proxy. Kudos for working on a project that is sooooo much faster than iptables. Those packet latency charts are wild.