18:00:03 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:03 Meeting started Tue Oct 26 18:00:03 2021 UTC. 18:00:03 This meeting is logged and archived in a public location. 18:00:03 The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:03 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:03 #chair mboddu nirik pingou mobrien nb 18:00:03 Current chairs: mboddu mobrien nb nirik pingou 18:00:03 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:03 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:03 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:03 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:04 #info reminder: speak up if you want to work on a ticket! 18:00:06 #topic Tickets needing review 18:00:08 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:34 just one infra one: 18:00:40 .ticket 10295 18:00:41 nirik: Issue #10295: Please create a mailing list for sysadmin-openshift users - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10295 18:00:52 med/med/ops and I asked some questions on it already. 18:01:09 Here here 18:01:24 * nirik just modified it. 18:01:29 hey mboddu any releng ones today? 18:01:40 Nope 18:02:13 cool. 18:02:21 #topic Upcoming work / planning 18:02:40 I'm just treading water this week. ;) will try and file some more after freeze pr's 18:03:13 and clear some more tickets. 18:03:33 hopefully we have our final rc, but time will tell 18:04:12 #topic Discussion / AOB 18:04:37 nirik: Any update on moving our s390x to z15? 18:04:39 anything folks would like to discuss? any issues, pr's, good movies, ? 18:04:56 mboddu: I have not seen any update on it. I can try asking around. 18:05:08 nirik: Thanks that would be helpful 18:05:21 I have one question 18:05:34 Im working on this one 18:05:47 .releng 10354 18:05:48 pmoura: Issue #10354: create epel-next-release-latest-8.noarch.rpm symlink - releng - Pagure.io - https://pagure.io/releng/issue/10354 18:06:12 .hi 18:06:13 nb: nb 'Nick Bebout' 18:06:17 mboddu: asked internally, will let you know what I find out. 18:06:33 Thanks nirik 18:06:39 <-- nothing new to add. Been quite busy at work and outside of work the last few days 18:06:53 * mboddu waits for pmoura questions 18:07:22 should i update the function update_epel_release_latest or write a new? I intend to update it and right now Im writing tests to be sure I wont break it 18:07:54 pmoura: Update the existing one 18:08:01 ok, thanks 18:08:27 I'd say it's up to you... whatever makes the most sense. If it can re-use more from the old one I'd update that... 18:09:56 I think it can be reused I got that question just because the name of it, it says latest and the link symlink will be "next" 18:10:55 ah yeah, confusing mix of terms there. :) 18:11:14 Yeah, but I think using the existing one makes more sense to me 18:12:32 * nirik nods 18:12:43 ok, anything else from anyone, or shall we call it a standup? :) 18:13:20 Nothing from me 18:13:47 ok, thanks for coming everyone! 18:13:50 #endmeeting