18:00:12 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:12 Meeting started Tue Jun 16 18:00:12 2020 UTC. 18:00:12 This meeting is logged and archived in a public location. 18:00:12 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:12 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:13 #chair cverna mboddu nirik smooge 18:00:13 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:13 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:13 Current chairs: cverna mboddu nirik smooge 18:00:13 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:13 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:14 #topic Tickets needing review 18:00:17 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:28 sure 18:00:37 or did we move it and I am int eh wrong channel? 18:00:47 no, we didn't... we talked about it, but didn't 18:01:03 ok hello everyone. I hope you all are well 18:01:10 we start off with an old old ticket 18:01:29 .ticket 8871 18:01:30 smooge: Issue #8871: [CI] Rawhide updates stuck in testing - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8871 18:01:34 you want to run the tickets today smooge ? fine by me... I can modify? 18:01:38 * mboddu here 18:01:41 sure 18:02:03 / 18:02:27 I guess wait on assignee? Also when does cverna move to his new manager role and should someone look to take this over? 18:02:55 not sure. 18:03:00 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#8871: bodhi, groomed, and 2 others https://pagure.io/fedora-infrastructure/issue/8871 18:03:01 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#8871 https://pagure.io/fedora-infrastructure/issue/8871 18:03:01 end of the month 18:03:22 .ticket 9031 18:03:23 smooge: Issue #9031: review-stats script cronjob timing issue - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9031 18:03:46 ha ha. I see what happened here. 18:03:50 openshift-prod-reviewstats 1Gi RWX Retain Bound messaging-bridges/openshift-prod-reviewstats 23h 18:04:00 messaging-bridges grabbed the wrong pv 18:04:17 I'll sort it out after meeting. 18:04:31 groomed openshift waiting-on-nirik 18:04:45 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#9031: OpenShift, groomed, and 2 others https://pagure.io/fedora-infrastructure/issue/9031 18:04:46 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#9031 https://pagure.io/fedora-infrastructure/issue/9031 18:04:57 .ticket 9035 18:04:58 smooge: Issue #9035: redo maintainer-test instances with large / partition - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9035 18:05:10 mobrien[m]: was working on this. I need to answer his questions 18:05:47 low-trouble medium-reward groomed waiting-on-requestor 18:06:39 +1 18:06:42 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#9035: groomed, low-trouble, and medium-gain https://pagure.io/fedora-infrastructure/issue/9035 18:06:43 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#9035 https://pagure.io/fedora-infrastructure/issue/9035 18:06:44 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9035: "redo maintainer-test instances with large / partition" https://pagure.io/fedora-infrastructure/issue/9035#comment-658599 18:07:00 .ticket 9036 18:07:01 smooge: Issue #9036: FAS2 is broken on various IAD2 hosts - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9036 18:07:20 so... one thing I noticed. Is this just fedora 32/rhel8? 18:07:24 yes 18:07:34 I can add that info to the ticket. 18:07:39 we just need someone to dig into it. 18:08:10 medtrouble/gain/waiting on asignee? 18:08:14 yes 18:08:35 need to not look up possible solutions while running the meeting :) 18:08:49 .ticket 9037 18:08:50 smooge: Issue #9037: Make additional aws proxies in various regions - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9037 18:08:59 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#9036: authentication, groomed, and 2 others https://pagure.io/fedora-infrastructure/issue/9036 18:09:00 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#9036 https://pagure.io/fedora-infrastructure/issue/9036 18:09:01 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9036: "FAS2 is broken on various IAD2 hosts" https://pagure.io/fedora-infrastructure/issue/9036#comment-658601 18:09:14 this is generally a 'resilience' and looking at how we build proxies in aws versus other places 18:10:13 * nirik has been pondering if we should drop proxies, but it's still just idle thought 18:10:56 yeah.. it is probably something to look at 18:11:19 low trouble, medium gain, groomed, waiitng on assignee 18:11:31 I mean we could drop all proxies, and then just serve things like docs/websites from openshift with cloudfront in front. 18:11:33 well getting rid of proxies is something else :) 18:11:35 but will ponder on it more 18:11:44 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#9037: aws, groomed, and 2 others https://pagure.io/fedora-infrastructure/issue/9037 18:11:45 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#9037 https://pagure.io/fedora-infrastructure/issue/9037 18:12:17 nirik, I think mirrormanager would need a rethought but could run in something similar 18:12:27 .ticket 9038 18:12:28 smooge: Issue #9038: Mailman is sending unauthorized fedmsgs - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9038 18:12:38 ok I think I fixed this one.. but I am not sure 18:13:01 if it is still sending as phx2.fedoraproject.org i don't know where it is coded 18:13:29 yeah, I don't see any recent ones. 18:13:38 just these: 2020-06-16 18:13:24 [fedmsg.crypto.utils WARNING] No routing policy defined for "org.fedoraproject.prod.github.check_run" but routing_nitpicky is False so the message is being treated as authorized. 18:14:27 closed as fixed 18:14:49 ok. 18:14:57 hum, might have been looking at the wrong one 18:15:01 oh 18:15:06 well then unclosed as fixed 18:15:14 but indeed it looks fixed. 18:15:19 there's just other problems. ;) 18:15:23 can file new ones on those. 18:15:33 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#9038 https://pagure.io/fedora-infrastructure/issue/9038 18:15:34 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9038: "Mailman is sending unauthorized fedmsgs" https://pagure.io/fedora-infrastructure/issue/9038#comment-658604 18:15:51 .ticket 9040 18:15:52 smooge: Issue #9040: Error 503 from osbs.fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9040 18:16:18 no idea on this one, lets leave it for cverna. 18:16:32 who can also hopefully show us how to check/more about it for when he's away 18:16:43 high-trouble (move flatpaks to OBS) 18:17:19 does flatpacks block composes? 18:17:23 nope. 18:17:44 high-trouble, medium-gain, waiting-on-assignee, groomed 18:17:57 note we need to be trained on this by cverna 18:18:29 yup 18:18:35 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#9040: OSBS, groomed, and 2 others https://pagure.io/fedora-infrastructure/issue/9040 18:18:36 ack 18:18:36 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#9040 https://pagure.io/fedora-infrastructure/issue/9040 18:18:37 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9040: "Error 503 from osbs.fedoraproject.org" https://pagure.io/fedora-infrastructure/issue/9040#comment-658606 18:19:35 .ticket 9041 18:19:36 smooge: Issue #9041: Need: Fedora 32 aarch64 vm for testing - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9041 18:20:18 we can try an aws one. mobrien[m] can or I can later 18:20:19 I think you and spot talked about this while I was detailing this in ticket. Another mobrien[m] item? 18:20:26 * nirik nods 18:20:35 low-trouble, medium-gain, groomed aws 18:21:20 or something else? 18:21:25 +1 18:21:28 ack 18:21:54 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#9041: aws, groomed, and 2 others https://pagure.io/fedora-infrastructure/issue/9041 18:21:55 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#9041 https://pagure.io/fedora-infrastructure/issue/9041 18:21:56 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9041: "Need: Fedora 32 aarch64 vm for testing" https://pagure.io/fedora-infrastructure/issue/9041#comment-658608 18:22:40 .ticket 9043 18:22:44 smooge: An error has occurred and has been logged. Please contact this bot's administrator for more information. 18:22:54 private 18:22:58 ah ok that one is private 18:23:10 ok well any releng tickets? 18:23:17 No new releng tickets 18:23:32 Oh well, there is 18:23:40 .releng 9532 18:23:41 mboddu: Issue #9532: Updates created in side-tags ejected from push - releng - Pagure.io - https://pagure.io/releng/issue/9532 18:23:47 I will note nirik has been working on kojira problem all day also 18:24:04 Yeah 18:24:11 mboddu: yeah, bodhi is still not doing something right with side tags. 18:24:17 Seems like its a bodhi issue, sometimes they are not tagging right 18:24:22 and just pushing it to testing doesn't work, you need to make sure all the tags are right 18:24:30 Exactly 18:24:53 Who is going to look bodhi issues? cverna or ... ? 18:25:54 hopefully cverna for now, but longer term not sure. 18:26:05 Okay, I will ping cverna in the ticket 18:26:23 medium-trouble, high-gain, groomed? 18:29:07 Okay, going with that 18:29:10 And 1 more 18:29:12 yeah, sorry 18:29:21 +1 mboddu 18:29:43 .releng 9531 18:29:45 mboddu: Issue #9531: manually retire EPEL7-only packages in PDC - releng - Pagure.io - https://pagure.io/releng/issue/9531 18:30:14 hm? 18:30:19 carlwgeorge pinged me about them 18:30:31 Not sure why they didn't retire properly, I need to look into them 18:30:46 medium-trouble, medium-gain, groomed? 18:31:43 Okay, thats all I got 18:31:51 ack. 18:32:18 thanks everyone. 18:32:21 ok well in that case.. anything else for today or time to press the button frank? 18:32:28 #endmeeting