[00:16:25] legoktm: sory was out earlier but see it got sorted pretty quickly either way :) [07:55:47] I haven't used the decom script in a while (probably a year), and I just used it for two hosts and both had issues with the **Failed to wipe swraid, partition-table and filesystem signatures, manual intervention required to make it unbootable**: Cumin execution failed (exit_code=2) [07:56:04] Is that something to expect? [08:17:32] that's not expected, no. can you open a task for that and tag is with SRE-tools and Infrastructure-Foundations, please? [08:27:06] it's expected only ifnthe host is down (powered off or unreachable) [08:27:42] volans|off: no, both or them were up and running [08:27:46] moritzm: will open it! [08:27:51] thx [08:30:13] https://phabricator.wikimedia.org/T311593 thank you both [13:46:58] does someone know how to do a wildcard search on puppetboard? [13:47:20] https://puppetboard.wikimedia.org/query gives a 400 [13:59:15] sukhe: https://puppetboard.wikimedia.org/nodes then filter, but it's not efficient [14:00:47] XioNoX: yeah, also it's making Firefox go crazy :P [14:00:52] wish there was an API I could curl [14:59:15] do we have _a_ single place where I can view all hosts on which Puppet is currently disabled? [15:06:40] sukhe: for production, https://thanos.wikimedia.org/graph?g0.expr=puppet_agent_enabled%20%3D%3D%200&g0.tab=1&g0.stacked=0&g0.range_input=1h&g0.max_source_resolution=0s&g0.deduplicate=1&g0.partial_response=0&g0.store_matches=%5B%5D [15:07:30] ah great, thanks taavi! [16:03:33] Jynus mission log star date 4072; everything looks peaceful on route to sector 12; no signs of outages or other anomalies [16:07:31] captain, I am picking up a faint distress signal from sector 13 ... [16:25:03] liutenant ori, plot an intecept course towards the Kobayashi Maru in sector 13. It is an order! [16:36:05] Would a kind admin on wikitech be willing to delete https://wikitech.wikimedia.org/wiki/Puppet_coding/Testing ? I've merged the contents into [[Puppet/Testing]] alongside another article (https://wikitech.wikimedia.org/w/index.php?title=Puppet/Testing&oldid=1992914) [16:38:15] brett: would it suit you to make the page a redirect instead? has the advantage that incoming links will all still work [16:38:49] Ah, oops, I totally fuzzed on that. Will make a redirect, thanks :) [16:38:53] 👍 [16:39:19] done, gracias [16:39:50] thanks for cleaning those pages up! [16:53:15] What is the Help: namespace designated for? i.e. what content for Puppet belongs under Help: and what under Main: ? [16:55:30] currently generally Help: is for user-facing WMCS documentation and the mainspace for production documentation [16:56:44] taavi: Thanks for the clarification! [16:57:05] Any qualms with me conveying that in Help:Main_Page? [16:58:07] the mainspace part already is kind of [16:59:29] although now I see that some of the WMCS user-facing docs are in Portal: (which actually isn't a real namespace), so I'm not sure about the difference between Help: and Portal: anymore [17:11:54] I am at the WMF office. It's weird :) [17:12:15] Long time heh? [17:18:48] yea, like 3 years or more [17:18:51] more like 4 I guess [17:19:50] taavi: originally the "Portal:" pseudo namespace on wikitech was just for intro pages about the various major sub projects (cloud vps, toolforge, data services, SRE). At some point Sarah moved a bit more content into subpages there, but I think generally that's still the intent. [17:23:05] brett: generally, all SRE things should live in the main namespace on wikitech. Help: is for Cloud Services user facing docs. Obsolete: is for old junk. OfficeIT: is an experiment that really went nowhere. Nova Resource: is for Cloud VPS project specific docs. Hiera: is an old thing that is not used anymore. [17:23:36] Tool: is for Toolforge/Cloud VPS hosted tool docs [17:24:02] * bd808 wonders where this should actually get written down on wikitech... [17:24:38] MediaWiki:SiteNotice ? :-P [17:25:05] * bd808 waves a trout in hauskatze's general direction ;) [17:25:24] lol [17:26:15] the Main_Page. since it already has sections for Toolforge, cloud VPS, SRE ... [17:26:40] could just add a sentence below each of the icons [17:56:56] Er, now could a kind admin please delete the [[Puppet/Testing]] page? I moved the old unmaintained content to [[Obsolete:Puppet/Testing]] and need the redirection page gone so I can move [[Puppet coding/testing]] into [[Puppet/Testing]] [18:02:45] Move succeeded Puppet coding/testing [18:02:45] Jump to navigation [18:02:45] Jump to search [18:02:46] "Puppet coding/testing" has been moved to "Puppet/testing" [18:03:14] mutante: Thanks so much :) [18:03:26] np [18:03:52] mutante: Sorry to be a pain, but shouldn't it be with an upper T? [18:04:09] (That's where the troublesome redirect is) [18:04:54] I think it's not capitalized. it wasn't before [18:05:36] might be confused what you wanted to achieve [18:05:57] looking [18:06:41] now there is "Puppet/Coding and style guidelines" [18:06:46] I meant shouldn't it be with an upper T as in the style guidelines for subpages [18:07:09] AFAIK subpages should be a separate sentence-case [18:07:41] "Puppet/testing" already says "See also: Puppet coding/Testing" [18:08:00] you want that to move to "Puppet/Testing" as well? [18:08:01] and it shouldn't, I'll fix that after this is resolved :) [18:08:35] I can't move Puppet/testing to Puppet/Testing [18:08:38] The page could not be moved, for the following reason: [18:08:46] oh, wait [18:08:50] Yeah, it's cause it already exists as a blank page [18:08:57] Hence the request for deleting it :) [18:09:25] "Puppet/testing" has been moved to "Puppet/Testing" [18:09:26] A redirect has been created. [18:09:28] check now [18:09:47] sorry, I have 3 pings at once :p [18:09:48] beautiful. Thank you! [18:11:20] :) np [18:12:16] brett: Dzahn talk contribs block changed group membership for BCornwall from (none) to administrator :p [18:12:27] oh no [18:12:29] :) [18:13:02] ha! [18:13:23] brett: now I know where to come if I need admin support [18:13:33] oh noooo [18:13:39] haha [18:14:44] I realize now there is "admin" and then there is "content admin" [18:14:57] win 27 [18:15:02] for whatever the real difference is [18:15:31] Hm, perhaps content admin doesn't have access to user creation/deletion and underlying stuff [18:16:50] content admin == admin except the edit interface abilities brett [18:17:13] and then "interface admin" https://www.mediawiki.org/wiki/Project:Interface_administrators [18:17:33] admin = both [18:17:36] aha [18:17:53] false [18:17:56] mutante: I don't think admins have IA rights, that's the whole idea of splitting IA [18:18:31] 'content admin' = can do most things admins can, but not edit interface messages or override the title blacklist, split from normal admins for BEANS reasons [18:18:37] you just said that's content admin though [18:19:05] 'interface admin' lets you edit sitewide css and js, which is separate from editing normal interface messages [18:20:01] alright [18:23:32] content admin is likely what brett wants. it's generally enough and due to wikitech's special nature in our ldap account management the extra perms the normal admin role has are somewhat more dangerous than usual [18:25:35] I want what is most agreeable to the team. Happy to help out wherever I'm needed, but if the elevated permissions are too much it can be made more conservative [18:25:52] taavi: so it _IS_ true that "Administrator" contains both content-admin AND interface admin, or it's not [18:26:01] NO [18:26:15] interface admin is an extra set of rights on top of the admin group [18:27:01] mutante: content-admin doesn't have `editinterface` or `tboverride` which sysop has; but neither Content Admins nor Admins have editsitecss, editsitejs, editsitejson, etc. These were split from sysops a couple of years ago. [18:27:15] taavi: Thanks for the explanations; Presentation could use a little more work, though ;) [18:27:57] indeed [18:28:41] it makes more sense on ~all other wikis where 'content admin' doesn't exist [18:28:59] i.e. everywhere else but Wikitech :) [18:31:15] changed group membership for BCornwall from administrator to content administrator [18:31:39] changed group membership for Dzahn from bureaucrat and administrator to bureaucrat and content administrator [18:31:49] groups you can't change: bureaucrat [18:32:07] taavi: fixed (mostly) [18:32:17] thanks! [19:29:05] wikitech's permissions are weird still I think compared to the project wikis. mostly historical reasons I would guess. there is a WP:BEANS thing with having interface admin perms there, but we trust all SREs to not put those beans up anyone's nose ;) [19:43:46] we're not exactly short on beans, it's true [19:44:44] And now it's simpler than it used to be, with all those OpenStack permissions e.g. cloudadmin [21:42:45] Hello team, I'm failing to understand where does Puppet takes the value of the resource title in 'puppet/modules/httpd/manifests/mod_conf.pp' line 17. [21:42:46] Do you know where is it taking it from and how could I edit it? [21:42:46] https://github.com/wikimedia/puppet/blob/93906b3e2b979f9f3f970cfbd25f31f2fb2c6218/modules/httpd/manifests/mod_conf.pp#L17 [21:43:21] The value is defaulting to 'php7.3' and I need to update it to 'php7.4' for Debian's Bullseye. [21:45:39] denisse|m: $title is a special variable and it contains the name of the resource wherever it is used [21:45:56] modules/noc/manifests/php_engine.pp: httpd::mod_conf { 'proxy_fcgi': [21:46:11] here 'proxy_fcgi' will be the $title [21:46:53] httpd::mod_conf { 'php7.4': ... for you [21:47:07] or httpd::mod_conf { $php_module [21:47:21] and some other code to set it to the right value before that [21:48:04] if (debian::codename::ge('bullseye')) { [21:48:37] $php_module_name = 'php7.4' [21:48:39] ... [21:48:54] httpd::mod_conf { $php_module_name [21:48:55] or so [21:49:05] sorry, gotta run away from computer [23:18:04] Thanks mutante, I still fail to see where on the repository it's getting the 'php7.3' value from. :(