18:00:24 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:24 Meeting started Mon Oct 10 18:00:24 2022 UTC. 18:00:24 This meeting is logged and archived in a public location. 18:00:24 The chair is phsmoura_. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:24 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:24 #chair nirik mobrien aheath1992 smooge 18:00:24 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:24 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:24 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:24 Current chairs: aheath1992 mobrien nirik phsmoura_ smooge 18:00:24 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:33 morning 18:00:34 hello phsmoura_ 18:00:57 hi Ebeneezer_Smooge 18:01:07 morning 18:01:18 hi nirik 18:01:55 #info reminder: speak up if you want to work on a ticket! 18:01:55 #topic Tickets needing review 18:02:01 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:02:20 .ticket 10928 18:02:21 phsmoura_: Issue #10928: fedorapeople.org https cert expired today - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10928 18:02:51 So this one was created last week, I think nb did it 18:02:53 ok this one is a needs a plan 18:03:06 nb did an emergency fix but it needs a long term plan 18:03:29 well.... 18:03:39 going from what nirik said earlier 18:03:44 sorry typing slowlyg 18:03:52 ok, so Im going to change its priority so it doesnt appear on this fileter anymore 18:04:02 yes, we can go back to digicert (which has some advantages) or automate the letsencrypt process. 18:04:03 filter* 18:04:48 I've not had a chance to think about which is best... go ahead and assign it to me... 18:04:53 .ticket 10932 18:04:54 phsmoura_: Issue #10932: Update sponsors of council FAS group - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10932 18:05:04 I can do this right now 18:05:42 ok, new contributor in cpe. just saw him on twitter :) 18:06:40 can we go to the next one? 18:06:45 done, closed. next 18:06:58 .ticket 10933 18:06:59 phsmoura_: Issue #10933: DANE record does not match on fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10933 18:07:20 med med ops I guess... 18:08:00 done 18:08:14 .ticket 10935 18:08:15 phsmoura_: Issue #10935: Please create a communishift repo for for me to play with - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10935 18:08:34 low,low,ops? 18:09:31 does this need some feedback from the communishift people on where repos and such are to be built? 18:09:39 or is that already publshed somewhere? 18:10:17 well, yes, it needs more info from mattdm... 18:10:32 and yeah, low, low ops sounds fine. 18:11:03 I mean, I am not sure where he wants this, if there's something besides a git repo involved or what. But I can look at finding that info 18:12:06 Hi 18:12:20 hi 18:12:20 ok, thats it for infra. lets move to releng 18:12:39 #info https://pagure.io/releng/issues?status=Open 18:12:48 .releng 11077 18:12:49 phsmoura_: Issue #11077: F38: System-wide change: RpmSequoia - releng - Pagure.io - https://pagure.io/releng/issue/11077 18:13:57 is it to evaluate the impact? 18:14:06 I don't think there's any inpact... so we can thank them and close. 18:14:24 ok, I can close it 18:15:44 done 18:15:50 .releng 11078 18:15:51 phsmoura_: Issue #11078: Problem email matching Pagure-Bugzilla when requesting new repository - releng - Pagure.io - https://pagure.io/releng/issue/11078 18:17:21 I think they may have figured it out, but we should keep it open to confirm? 18:17:28 or ask them to confirm in the ticket? 18:17:54 sure, let me ask in the ticket 18:20:21 should we tag this issues as well? or wait until tomorrow so we can see if theres any feedback? 18:21:33 lets wait until tomorrow. 18:21:58 ok 18:22:04 moving to open floor 18:22:06 #topic Planning, Upcoming work and Open floor 18:23:02 I am digging again into FMN... it's currently running, but processing so slowly it might as well not be running. 18:23:07 power outage seems to be still going on in BOS office 18:23:17 If we can't get it working again soon, I am going to have to swap the old one back in 18:24:54 also there's go/no-go meeting thursday... still no RC yet 18:25:06 I'm also out all next week. But am here this week. ;) 18:25:49 SO Im updating the firmware of our infra. I found a python lib that can give me all the info but couldnt make it work yet. 18:27:02 nirik: also some of the machines I could gather info last week stopped responding my requests 18:28:46 phsmoura_: odd. I do know some of them reject you if you make too many failed attempts... 18:28:54 but otherwise they should all be working 18:29:46 "well, yes, it needs more info..." <- I was just providing the info that the presentation today said would be needed :) 18:29:58 also, just to make sure... you are just gathering the information right? we do probibly want to update the firmware, but we should do that in an outage or at least after f37 is out... don't want to mess up anything yet. :) 18:30:23 mattdm: ok, I'll have to watch that, because I wasn't there and have no context. ;) 18:30:59 So maybe I was blocked when tried to get the info using the script? yes, Im just gathering info and because I need to do in the whole net Im trying to automate the task 18:32:44 phsmoura_: cool. yeah, automation is a great idea there. Yeah, if the script didn't have the right info in it... but usually it just blocks for like 10min or something 18:34:02 ok, so I should be able to do it again. thanks, Ill be more carefull while Im still writing the script 18:34:40 * nirik had nothing else today 18:35:16 we passed the time a bit, anything else please feel free to reach fedora-admin or fedora-noc 18:35:23 thanks all for attending 18:35:31 #endmeeting