18:00:07 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:07 Meeting started Wed May 26 18:00:07 2021 UTC. 18:00:07 This meeting is logged and archived in a public location. 18:00:07 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:07 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:07 #chair mboddu nirik pingou mobrien nb 18:00:07 Current chairs: mboddu mobrien nb nirik pingou 18:00:07 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:07 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:07 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:07 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:09 #info reminder: speak up if you want to work on a ticket! 18:00:11 #topic Tickets needing review 18:00:13 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:15 Hello, I am here 18:00:20 * nb is not really here 18:00:59 * nb is IRC dumpster fire fighting 18:00:59 hey mboddu. 18:01:05 nb: thanks for that! 18:01:19 .ticket 9979 18:01:20 nirik: Issue #9979: Notifications from bugzilla aren't nicely formatted/summarized - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9979 18:01:26 I can update the tickets 18:01:29 this is related to or possibly a dupe of another one 18:01:46 https://pagure.io/fedora-infrastructure/issue/9820 18:01:48 Yeah 18:02:05 Sorta related, but entirely 18:02:17 not entirely* 18:02:22 * mboddu needs more tea 18:02:22 it's likely the same cause/same place to fix it. 18:02:27 nb: keep on going 18:02:45 nirik: Close as dupe? 18:02:50 so, I guess close it a dupe and add info about it to the main one? 18:02:52 yeah. 18:02:56 FYI everyone - no more matrix bridges for now, until libera bridges are ready 18:03:02 Okay 18:03:27 thats it on infra. Any releng? 18:03:47 Yea 18:04:13 .releng 10134 18:04:14 mboddu: Issue #10134: Shorten side-tag merge window by tagging builds after being singed all of them - releng - Pagure.io - https://pagure.io/releng/issue/10134 18:04:43 this is something that sounds easy, but is... not at all. 18:04:48 Yeah 18:04:55 Maybe add a staging tag inbetween? 18:04:56 med/med/ops? med/high/ops? 18:05:03 +1 18:05:14 well, how does robosignatory know something is a bundle? 18:06:00 Nope, instead of going from fxx-pending to fxx, update robosig config as fxx-pending to fxx-staging and once everything is signed, then move to fxx 18:06:23 but what does 'everything' mean? idle? what if 100 unrelated builds come in? 18:06:51 I think we would need a manual step. 18:07:02 The problem is waiting on signing, they want to sign everything before making it available in buildroot 18:07:39 Actually, we used to enable signing on side tags, but we kinda stopped doing it since we were really not creating many side tags lately 18:07:45 So, just bring that back? 18:07:55 we could. it's kinda a pain... but it would solve this. 18:08:04 Yeah 18:08:30 I'm fine saying that...so in adding side-tags, we should ask if they want them signed or not. 18:09:04 we should ask about the f35-python one 18:09:06 Yeah 18:09:14 On it already 18:09:40 ok, any other tickets in releng? 18:10:02 .releng 10135 18:10:03 mboddu: Issue #10135: python-pytest-freezegun is owned by the fedora-scm-requests operator, doesn't have the main alias - releng - Pagure.io - https://pagure.io/releng/issue/10135 18:10:17 low, low, ops for the fix 18:10:48 But the problem is sometimes, pagure times out and assigns the project to whoever processed the ticket 18:11:02 Make fedscm-admin more reliable? 18:11:11 yeah, I guess. 18:11:18 if there is some way to do that. ;) 18:11:19 Which is a higher ask :D 18:11:26 Exactly :) 18:11:27 or... have it be able to detect this and fix it? 18:11:50 Could be, let me comment on the ticket 18:12:02 That is all 18:12:40 #topic work plans / upcoming tasks 18:12:40 #info everyone should note what things they are hoping to work on over the next day/week 18:12:48 #info friday is a red hat recharge day 18:12:53 #info next monday is a holiday 18:13:09 any other things we have planned for this week? 18:13:13 in us ? 18:13:32 mboddu: BTW, I started to do a cron for side-tag cleanup... but the script actually doesn't work. ;( Need to figure out why 18:14:02 copperi: Yes, in US we have both Fri and Mon as holidays 18:14:11 ok 18:14:16 nirik: Let me know if I can help 18:14:54 will do 18:15:03 #topic Discussion items 18:15:12 any tickets, blockers, pr's or anything to discuss? 18:15:42 nirik: No rawhide compose kicked off last night 18:15:53 mboddu: oh? huh. 18:16:12 nirik: I noticed it just before the meeting 18:16:28 I couldn't see why, but I am kicking off one now 18:16:33 ha. I see why 18:16:37 no wait 18:16:48 missing nfs mounts. 18:16:51 fixed now 18:17:30 Oh, nvm me, I checked the nfs mounts on bodhi-backend01 thinking I am on rawhide box :D 18:17:31 so go ahead now. :) 18:17:58 That is all 18:18:03 w.r.t. ... "Provide email alias allowing to contact EPEL maintainers ", I wanted to start working on that, but I am not sure what alias should I create? currently $(package)-maintainers seems to email everybody with certain level of acccess to the package in src.fp.o ... should I create new alias? 18:18:22 asaleh: yeah. 18:18:36 something like $(package)-epel-maintainers ? 18:18:59 ok, I can do that :) 18:19:02 and I suppose for symetry we should change the existing one to fedora-maintainers and the old one to go to both? 18:19:55 +1 18:19:57 ie, have 3 aliases, one for fedora one for epel and one for both? 18:20:05 Agreed 18:20:40 or I will create epel-maintainer and fedora-maintainer that sends to just the primary(?) maintainer, pagure already has that through bzoverrides, and -maintainers is the "email everybody" 18:21:36 hum, yeah. I guess if someone has a specific epel contributors they would want them only to get epel ones? 18:21:49 so is https://apps.fedoraproject.org/calendar/ a infrstructure issue or website issue 18:22:09 infra... 18:24:20 asaleh: I guess we could discuss more in ticket? or on list... 18:24:29 Any other items? 18:24:39 None from me 18:26:25 ok, thanks everyone! 18:26:27 #endmeeting