19:00:19 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:19 Meeting started Wed Nov 8 19:00:19 2023 UTC. 19:00:19 This meeting is logged and archived in a public location. 19:00:19 The chair is phsmoura. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:00:19 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:19 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:19 #chair nirik smooge phsmoura 19:00:19 #meetingname fedora_infrastructure_ops_daily_standup_meeting 19:00:19 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:19 #info agenda is at https://board.net/p/fedora-infra-daily 19:00:19 Current chairs: nirik phsmoura smooge 19:00:19 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:24 morning 19:00:30 hello again 19:00:57 we meet again! :) 19:02:15 #info reminder: speak up if you want to work on a ticket! 19:02:15 #topic Tickets needing review 19:02:32 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:02:44 .ticket 11608 19:02:45 phsmoura: Issue #11608: [Matrix] Request for admin to @fca:fedoraproject.org in several spaces - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11608 19:03:13 low low ops, assign to me 19:03:17 I just need to do it. 19:03:18 +1 19:03:50 .ticket 11610 19:03:51 phsmoura: Issue #11610: GnuTLS: One of the involved algorithms has insufficient security level. - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11610 19:04:02 .hi 19:04:07 aheath1992: aheath1992 'Andrew Heath' 19:04:08 hello 19:04:31 I'm not sure whats going on here. 19:04:43 i put some notes in 11610 and without more info from reporter.. meh 19:04:57 yeah... we need context here. 19:05:04 and likely there is nothing we can do. 19:05:25 low low ops 19:05:30 waiting on reporter? 19:05:47 well the only thing is if it is something with F39+ default security we could have mirrormanager put that in as a test and say 'you aren't a good system' 19:06:18 if it is instead a 'I set my system security to FUTURE and HIGH' then nothing we can do 19:06:34 I think it's very unlikely any f39 change. 19:06:41 we would have seen it before. 19:07:08 i didn't think so but left it as a possibility of a 'woops' 19:07:45 the FUTURE people don't realize how much of the internet won't work for them... 19:07:51 yep 19:07:56 until they reach the future 19:08:20 you can't make the future come faster by setting something in a config file 19:08:55 .ticket 11611 19:08:56 phsmoura: Issue #11611: add monitoring for dnf countme - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11611 19:09:09 that is the problem you found nirik somewhere else? 19:09:21 yes, I think this is fixed now. 19:09:40 probably needs someone to rn the old logs (hopefully) 19:09:43 I am not sure when it will update tho... I think nils was re-running it? 19:10:23 * nirik isn't sure what the pipeline looks like there. 19:10:30 not sure either. 19:11:03 If the scripts are running correctly, then the /var/lib/countme may be up2date but the /var/www/html//countme may not be 19:11:04 anyhow, should we just close it as fixed? or wait until we confirm? 19:12:14 not fixed 19:12:49 ok. So, how about high gain, med trouble, ops, assign to nphillip? 19:12:52 or something else is broken with it. the files in /var/lib/countme aredated from Oct26 when they should be today (some others look newer but not the ones I was expecting) 19:13:03 yeah 19:13:45 oh, also here... we need a nagios check 19:13:59 to alert if it's not updated in a day or two? 19:14:14 countme 1707020 0.0 0.0 12852 2376 pts/0 S+ Sep24 0:07 /bin/sh -e ./mirrors-countme/scripts/countme-regenerate-dbs.sh 19:14:20 may also be a problem? 19:15:00 but could be working as expected. anyway.. +1 to high gain/med trouble / nphillip 19:15:03 might. please note in the ticket 19:16:17 updated 19:16:38 but I think the expired fedora messaging cert is the cause for it stopping on the 26th... but not sure why the manual run didn't update it... 19:17:25 we can move on. ;) 19:17:46 #info https://pagure.io/releng/issues?status=Open 19:17:58 .releng 11773 19:18:01 phsmoura: Issue #11773: No new stable Silverblue/Kinoite/Sericea/Onyx compose since 39.20231103.n.0 - releng - Pagure.io - https://pagure.io/releng/issue/11773 19:18:22 yeah, so, this one is caused by the ref not changing to link to updates after release. 19:18:28 but I can't recall what does that... 19:18:32 med med ops 19:19:04 .releng 11774 19:19:04 and I messed up the changes phsmoura made to the countme ticket so redoing.. 19:19:05 phsmoura: Issue #11774: Stalled EPEL package: Krusader - releng - Pagure.io - https://pagure.io/releng/issue/11774 19:19:59 np 19:20:06 low low ops? 19:20:07 +1 19:20:31 #topic Planning, Upcoming work and Open floor 19:21:32 So my plan: today: merge pending pr's and deploy them, close some tickets, file outage ticket for next week. Tomorrow/friday: catch up on post freeze stuff, possibly reinstall some machines with rhel9. 19:21:50 next week: outage wed/thrusday for mass update/reboot. 19:22:01 week after: thanksgiving week in the us, will be out all week. ;) 19:22:09 Have some PR's coming through if me and Git and get along 19:22:31 git doesn't git along with any of us gits. 19:23:42 * nirik has nothing more off hand 19:23:48 Did Pr to redirect start page https://pagure.io/fedora-infra/ansible/pull-request/1623 now reviewing files to open PR for planet in OCP 19:24:07 great! 19:25:06 I'll work thru pr's from oldest to newest (in a while, still need to catch up on email and epel meeting this afternoon) 19:25:38 thats all I think 19:25:53 thanks everyone :) 19:26:12 #endmeeting