[04:25:03] umm.. how were the issues enabled on https://gitlab.wikimedia.org/toolforge-repos/spacemedia/-/issues? [11:04:05] Good question, I'm not aware of any plans to enable issues for additional projects but maybe RelEng know something about it. [12:18:36] Issues are disabled by default for new projects. But project maintainers can enable them per-project. afaik there is not option to disable this feature completly, see https://gitlab.com/gitlab-org/gitlab/-/issues/2538 [16:58:46] dduval, mutante: I merged the proxy change for adding http proxy to buildkit. [17:00:05] I noticed Shared Runners in WMCS also running buildkit but they fail to come up and throw error messages around fork/exec permission denied. It this intended? Or do we want buildkit only on Trusted Runners? [17:49:49] 10GitLab (CI & Job Runners), 10Release-Engineering-Team (Priority Backlog πŸ“₯): Remove use custom network for GitLab runners and buildkitd in favor of a fixed IP - https://phabricator.wikimedia.org/T317904 (10dduvall) [17:50:49] 10GitLab (CI & Job Runners), 10Release-Engineering-Team (Priority Backlog πŸ“₯): Remove use custom network for GitLab runners and buildkitd in favor of a fixed IP - https://phabricator.wikimedia.org/T317904 (10dduvall) [18:30:35] 10GitLab (CI & Job Runners), 10Release-Engineering-Team (Priority Backlog πŸ“₯): Remove use custom network for GitLab runners and buildkitd in favor of a fixed IP - https://phabricator.wikimedia.org/T317904 (10dduvall) Well, I seem to be running into a catch 22 here: Fixed IPs are only supported when using a cust... [21:48:44] 10GitLab (CI & Job Runners), 10Release-Engineering-Team (Priority Backlog πŸ“₯): Remove use custom network for GitLab runners and buildkitd in favor of a fixed IP - https://phabricator.wikimedia.org/T317904 (10dduvall) [21:49:23] 10GitLab (CI & Job Runners), 10Release-Engineering-Team (Priority Backlog πŸ“₯): Explicitly config buildkitd with internal DNS nameserver - https://phabricator.wikimedia.org/T317904 (10dduvall) [21:50:17] 10GitLab (CI & Job Runners), 10Release-Engineering-Team (Priority Backlog πŸ“₯): Explicitly config buildkitd with internal DNS nameserver - https://phabricator.wikimedia.org/T317904 (10dduvall) I've updated the task as abandoning the custom network no longer seems feasible, and there appears to be a way to config... [21:50:40] 10GitLab (CI & Job Runners), 10Release-Engineering-Team (Priority Backlog πŸ“₯): Explicitly config buildkitd with internal DNS nameserver - https://phabricator.wikimedia.org/T317904 (10dduvall) p:05Triageβ†’03Medium [23:34:23] mutante: is there a canonical way to reference the nameservers of the host in puppet code? i see that `profile::resolving::nameservers` is the way we configure them in hiera, but i also see some references in puppet to `$::nameservers` and i'm wondering if that's a puppet fact or something [23:35:05] i've found a way to configure buildkitd's nameservers explicitly thankfully. i just need to add the right puppet code to get its configuration populated [23:35:58] i thought maybe i could do `lookup('profile::resolving::nameservers', { default_value => $::nameservers })` but that seems a little weird to do from a module. i don't know... [23:36:38] taking a look [23:37:22] ok, thanks! [23:38:55] I do not see name servers in the output of facter (puppet facts), unlike IP, netmask, and so on [23:39:22] probably the same way as the base module gets them to put into resolv.conf [23:39:29] give me a moment [23:42:08] profile::resolving uses class {'resolvconf': [23:42:28] as you say takes it from profile::resolving::nameservers [23:43:42] "facter nameservers" does not return an error but is also empty [23:44:05] Interesting, ok [23:44:14] I see $::nameservers used in toolforce, labs/ores, [23:44:18] that is cloud specific [23:44:21] Maybe it’s in labs or something [23:44:23] Right [23:44:29] yea, I dont think it means anything in prod [23:44:32] the other one does [23:44:38] the ones in Hiera [23:45:00] now maybe we can reuse class {'resolvconf" ? [23:45:06] if that's what you need [23:45:53] # @summary simple class to configure resolv.conf [23:45:54] No I need the nameservers as a structured variable so I can write it to buildkkitd.toml [23:46:29] ok, gotcha [23:46:33] so Array[Stdlib::Host] $nameservers = lookup('profile::resolving::nameservers'), then I would say [23:46:35] I’ll try something with profile::resolving and submit for review! [23:46:39] in a profile class [23:46:42] any profile class [23:46:55] sounds good [23:46:56] ah ok. Perfect [23:47:00] Thank you! [23:47:42] copied from modules/profile/manifests/resolving.pp [23:47:44] yw