16:00:35 #startmeeting Infrastructure (2022-04-28) 16:00:35 Meeting started Thu Apr 28 16:00:35 2022 UTC. 16:00:35 This meeting is logged and archived in a public location. 16:00:35 The chair is eddiejennings. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:35 The meeting name has been set to 'infrastructure_(2022-04-28)' 16:00:50 #meetingname infrastructure 16:00:50 The meeting name has been set to 'infrastructure' 16:00:51 #chair nirik siddharthvipul mobrien zlopez pingou bodanel dtometzki jnsamyak computerkid 16:00:51 #info Agenda is at: https://board.net/p/fedora-infra 16:00:51 Current chairs: bodanel computerkid dtometzki eddiejennings jnsamyak mobrien nirik pingou siddharthvipul zlopez 16:00:51 #info About our team: https://docs.fedoraproject.org/en-US/cpe/ 16:00:51 #topic greetings! 16:00:56 .hello aheath1992 16:00:57 aheath1992: aheath1992 'Andrew Heath' 16:00:59 .hi 16:01:01 eddiejennings: eddiejennings 'Eddie Jennings' 16:01:01 morning 16:01:07 Greetings all! :D 16:01:22 .hi 16:01:23 nb: nb 'Nick Bebout' 16:02:12 #topic New folks introductions 16:02:12 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 16:02:12 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 16:02:31 Anyone new with us this week? If so, say "hi" and introduce yourself! 16:02:36 .hello zlopez 16:02:37 mkonecny: zlopez 'Michal Konecny' 16:02:42 We won't bite. Not even nirik :) 16:03:18 .hello petebuffon 16:03:18 petebuffon: petebuffon 'Peter Buffon' 16:03:23 .hi 16:03:24 mobrien: mobrien 'Mark O'Brien' 16:03:28 🙋 16:03:33 zodbot is a bit sketchy 16:04:02 Yeah. It only accepts greetings through kneeling :D 16:04:04 There is a lag between matrix and libera.chat, I see only few messages on matrix 16:04:17 zlopez :( 16:05:27 Looks like we don't have any new folks this week. Let's move along. 16:05:50 .hello dkirwan 16:05:51 Saffronique: dkirwan 'David Kirwan' 16:06:00 #topic Next chair 16:06:00 #info magic eight ball says: 16:06:16 ##info chair 2022-04-28 - eddiejennings 16:06:16 ##info chair 2022-05-05 - dtometzski 16:06:16 ##info chair 2022-05-12 - 16:06:28 Any volunteers for May 12th? 16:06:31 Is it just me or has matrix stopped working? 16:06:44 zlopez said it was lagging 16:06:51 * nirik hands the matrix bridge a plunger 16:06:58 It doesn't work well today 16:07:11 I see only third of the messages 16:07:24 .hi siddharthvipul1 16:07:24 VipulSiddharth[m: Error: Missing "]". You may want to quote your arguments with double quotes in order to prevent extra brackets from being evaluated as nested commands. 16:08:08 Didn't know Zod would respond to commands from Matrix. That's curious. :) 16:08:45 After May 2nd, I'll know what my new work schedule will be, but until then I can't volunteer for meeting chair :( 16:08:55 ha ha ha. 16:09:07 it's because VipulSiddharth[m has a missing ] in nick... funny 16:09:48 Any takers for chairing 2022-05-12? We have next week covered, so worst case we decide it then, but it's nice to have 2 weeks out. 16:10:00 It's too long for IRC :-D 16:10:25 eddiejennings: I can take it 16:10:46 Sold to zlopez! 16:11:01 ##info chair 2022-05-12 - zlopez 16:11:12 Thank you! 16:11:27 #topic announcements and information 16:11:27 #info CPE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1030 Europe/paris in #centos-meeting 16:11:27 #info CPE Infra&Releng NA-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1800 UTC in #fedora-meeting-3 16:11:27 #info If your team wants support from the Fedora Program Management Team, file an isssue: https://pagure.io/fedora-pgm/pgm_team/issues?template=support_request 16:11:29 #info Fedora 36 Beta is out 16:11:31 #info Fedora Final freeze is on going 16:11:33 #info thread on fedoraplanet on infrastructure list, chime in if you have thoughts on it 16:11:35 #info please help us with improving contribution to fedora infra https://discussion.fedoraproject.org/t/improving-contribution-to-fedora-infrastructure/38294/8 16:12:06 Any other new announcements? 16:12:23 I've just opened the above link, so I *will* get to reading it and responding today :D 16:12:42 I need to still get back to the planet thread. Been burried. 16:14:01 We're still in Final Freeze for F36, right? 16:14:22 Yes, but we have RC compose :-) 16:15:06 Looks like there are no other new announcments. Let's keep moving. 16:15:24 #topic Oncall 16:15:24 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 16:15:24 #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/ 16:15:24 ## .oncalltakeeu .oncalltakeus 16:15:44 #info dtometzki on call from 2022-04-22 to 2022-04-28 (eddiejennings covering 2022-04-28) 16:15:44 #info nirik on call from 2022-04-29 to 2022-05-05 16:16:08 Any takers for 2022-05-06 - 2022-05-12? 16:16:17 .oncalltakeus 16:16:17 nirik: Kneel before zod! 16:17:49 As with the meeting chair, it's nice to have on-call planned at least 2 weeks out. 16:18:34 I can do that one 16:18:43 Thank you mobrien76 16:19:34 #info mobrien76 on call from 2022-05-06 to 2022-05-12 16:19:58 Speaking of on-call 16:21:02 #info Summary of last week: (from current oncall ) 16:21:21 I'm not sure if dtometzki is with us, but I don't recall seeing any pings. And there weren't any for the time I covered this morning. 16:22:46 There was one yesterday about spammers... but nb took that on 16:22:59 Ah, thanks nb :) 16:23:01 what a rabbit hole that is 16:23:18 Which, if we have any apprentices that have some spare time maybe? 16:23:35 It'd help if you could look through https://pagure.io/browse/projects/ and make a list of spammy-looking ones 16:24:06 I may be able to help with that once new work schedule is solid. 16:24:35 Moving along. 16:24:37 #topic Monitoring discussion [nirik] 16:24:46 #info https://nagios.fedoraproject.org/nagios 16:24:46 #info Go over existing out items and fix 16:24:55 nirik the stage is your's! 16:24:57 I think not much change here... 16:25:09 we continue to get badges and resultsdb alerts anoyingly. 16:26:23 I think we can move on. 16:26:31 after freeze I want to try and clean up all the little things... 16:26:46 Noted, and sounds like a plan! 16:27:22 I know two weeks ago petebuffon and I did the learning topic on Tor services. So last week would've been ticket backlog. 16:27:39 Was there a learning topic planned for this week? If not, we can look at tickets again. 16:28:24 I thought we had one, but I could be wrong. 16:28:34 perhaps we should try and brainstorm up a few ? 16:28:40 weird thing was immediately after the infra meeting I had a meetup about tor 16:29:22 i think last time we just came up with the last two learning topics 16:29:34 Something that I want to learn about is making and restoring backups / having a DR plan using btrfs snapshots. 16:29:57 eddiejennings: sounds like a nice talk... when would you like to give it? ;) 16:29:59 So I'd be happy to experiment with that in lab, and in two weeks present a learning topic about it 16:30:39 ya i like that, btrfs commands can be a bit tricky to remember 16:31:31 The general (maybe crazy) idea I'm wanting to test, is have my KVM VMs on a btrfs volume, somehow have that replicating to another physical server, and if disaster strikes, basically mount the snapshot on the other server and turn on the VMs. 16:31:41 Then replicate back to the original server when original server is fixed. 16:32:03 reminds me of drbd. ;) 16:32:10 eddiejennings, so like hyperconvirge with BTRFS 16:32:24 I could do a talk on terraform and aws some week if there was any interest? 16:32:40 mobrien76, I would be quite interested in that. 16:32:53 terraform++ 16:33:18 sure. +1 16:33:27 ok put me down at the next empty date 16:33:39 eddiejennings: We can talk about it offline if you want. 16:33:41 maybe a deep dive on an essential fedora app? 16:33:48 aheath1992, Something like that. The idea being that my VM storage is being replicated to another server fairly often so if something goes sideways, I can simply power on the VM from the other server until the original host is fixed. 16:34:03 ack 16:34:49 So learning topic for 2022-05-12 will be BTRFS replication / backup / restore by eddiejennings 16:35:32 and 2022-05-26 will be mobrien76 with into to AWS and Terraform? 16:35:42 sounds good to me. 16:35:46 +1 16:36:07 Ping me when you get started. There are some caveats, e.g. btrfs send/receive on nodatacow images. 16:36:18 I shall cmurf :) 16:37:17 #topic Upcoming learning topics 16:37:18 ## info BTRFS replication / backup / restore [eddiejennings] 2022-05-12 16:37:46 ## info Intro to AWS and Terraform [mobrien] 2022-05-26 16:38:27 Did we find out if there was a learning topic scheduled for today (with the 20 minute we have left)? 16:38:48 I didn't find any 16:38:58 yeah, seems not. 16:39:42 We can probably look at some tickets now 16:39:48 Sounds good. 16:40:02 #topic Fedora Infra backlog refinement 16:40:03 #info Refine oldest tickets on Fedora Infra tracker 16:40:03 #link https://pagure.io/fedora-infrastructure/issues?status=Open&order_key=last_updated&order=asc 16:40:25 .ticket 10099 16:40:26 eddiejennings: Issue #10099: bvmhost-x86-01.stg.iad2.fedoraproject.org lost a disk - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10099 16:40:53 yeah, I haven't done anything here... we have 3 machines that are needing disk replacement. 16:41:23 Noted. 16:41:36 .ticket 10528 16:41:37 eddiejennings: Issue #10528: src.fp.o: Cannot activate the "Prevent creating new branches by git push" hook - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10528 16:41:38 I guess I can try and deal with it... (he says, hoping mobrien76 might take it) 16:41:55 doh, jumped the gun. My apologies 16:42:10 Is there an SOP for disk replacement documented somewhere? 16:42:21 I'm curious what the steps look like... 16:42:48 nirikI have to drop offline now but I can have a look tomorrow. Bad news is that machine is out of warranty 16:43:00 cmurf: call dell, send them junk they ask for, they send a new disk to the dc, get tech approved to go in and replace it. 16:43:20 mobrien76: yeah, hit me tomorrow morning and we can look at the 3 and figure out what to do. 16:44:02 * nirik can update that ticket so it's not on the top still 16:44:18 Yeah I mean software end of things :) like is it a reinstall or restore of some kind. 16:44:28 ah, zlopez beat me to it 16:45:16 I added the backlog refinement comment :-) 16:45:16 cmurf: oh, no, it's reboot to make sure it's seen by the controller (optional), then mdadm commands to readd it to the array 16:45:35 Ahh ok 16:46:03 that part is easy. The calling and talking to people and getting thru paperwork is the anoying part. :) 16:46:12 speaking of, I'll probably be posting in ask Fedora soon about mdadm and some failed experiments in my lab :P 16:46:13 Always 16:46:47 How about 10528, any insight on that one? Looks like nirik was the last comment on it 16:47:22 ah yeah, I was hoping pingou would chime in there... I don't understand the error. Perhaps zlopez could look? 16:47:27 * aheath1992 interested in mdadm experiments 16:48:17 I can ping pingou again in the ticket perhaps? 16:48:47 pinging anyone with ping in their name seems to be the only prudent course of action :D 16:48:57 I can try to look at it, but my knowledge of pagure is not that deep 16:49:30 hum, looking at it again... I see why it's trying to do that... but not sure why it's denied. 16:50:06 Does the hook has correct ownership? 16:50:41 hum, not really. 16:50:46 it's a broken sym link. ;) 16:50:54 lrwxrwxrwx. 1 root packager 62 Nov 20 2018 /srv/git/repositories/requests/rpms/python-u-msgpack-python.git/hooks/pre-receive -> /usr/lib/python2.7/site-packages/pagure/hooks/files/hookrunner 16:51:04 This is probably your answer :-) 16:51:15 yeah. 16:51:17 python 2.7? 16:51:25 especially since pagure is using python3.6 16:51:27 yeah 16:51:46 Makes sense :) 16:51:48 let me fix that and see if it fixes the issue. 16:51:51 Is this symlink created by pagure or by ansible playbook 16:51:55 ? 16:52:20 It seems that we probably found the fix for the issue :-D 16:52:53 one more ticket 16:53:08 .ticket 10541 16:53:09 eddiejennings: Issue #10541: Nagios checks for pagure.io - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10541 16:53:46 zlopez: I think it's historical data from before we moved to 3.6. I don't know why it didn't get converted tho. 16:54:10 so on this one we were waiting for what to monitor. 16:54:12 eddiejennings: This one seems to be waiting for reporter 16:54:31 perhaps we should just brainstorm what makes sense here? but we don't know what it was that they noticed. 16:54:34 I will switch the status to Waiting on Reporter 16:55:17 Yeah. Status change would be appropriate 16:55:34 But https://pagure.io/fedora-infrastructure/issues makes sense to monitor, because if this doesn't work, people can't file tickets 16:56:08 well, monitor how? that it returns a 200? 16:56:30 That would be reasonable 16:56:35 look for HTTP 200 16:56:43 That should be simple enough 16:57:13 start with 200 get more advance if needed 16:57:25 +1 16:57:57 eddiejennings, I can take this one 16:58:17 Excellent 16:58:24 And for our last couple of minutes. 16:58:35 #topic Open Floor 16:58:42 ok, note that nagios is "fun" :) but it can do this. 16:58:50 Any other comments, announcements, etc? 16:59:45 * nirik has another meeting. Thanks folks. 17:00:11 eddiejennings++ 17:00:13 If someone can provide some background and information on https://pagure.io/fedora-infrastructure/issue/10509 i can get started on this ticket as well 17:00:16 eddiejennings++ 17:00:16 zlopez: Karma for eddiejennings changed to 7 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:00:36 And we've hit 13:00 on the east coast of the United States; thus. . . 17:00:37 #endmeeting