19:00:01 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:01 Meeting started Wed Nov 18 19:00:01 2020 UTC. 19:00:01 This meeting is logged and archived in a public location. 19:00:01 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:01 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:01 #chair mboddu nirik smooge pingou mobrien 19:00:01 Current chairs: mboddu mobrien nirik pingou smooge 19:00:01 #meetingname fedora_infrastructure_ops_daily_standup_meeting 19:00:01 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:01 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:01 #info agenda is at https://board.net/p/fedora-infra-daily 19:00:02 #topic Tickets needing review 19:00:03 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:00:08 * mboddu is here 19:00:44 morning. 19:01:08 who wants to mod tickets today? and should we trade off who runs them? I'm happy with whatever 19:01:22 I am 19:01:42 .ticket 9473 19:01:43 nirik: Issue #9473: Starting January 4, 2021, we will block all sign-ins to Google accounts from embedded browser frameworks - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9473 19:01:55 I opened this morning from an email I saw in the queue 19:02:04 I don't think this will be a issue... and if it is... it's going to be blocked on mailman upgrades. 19:02:20 so, IMHO, keep it in mind when/if it breaks, but dont worry about it now 19:02:57 if it does break, I hope we could ask upstream to fix it instead of us having to... 19:02:58 low/low/ops closed 19:03:25 +1 19:03:46 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9473 https://pagure.io/fedora-infrastructure/issue/9473 19:03:47 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9473: lists, low-gain, and 2 others https://pagure.io/fedora-infrastructure/issue/9473 19:03:48 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9473 https://pagure.io/fedora-infrastructure/issue/9473 19:03:49 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9473 https://pagure.io/fedora-infrastructure/issue/9473 19:03:50 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9473: "Starting January 4, 2021, we will block all sign-ins to Google accounts from embedded browser frameworks" https://pagure.io/fedora-infrastructure/issue/9473#comment-702259 19:03:51 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9473: "Starting January 4, 2021, we will block all sign-ins to Google accounts from embedded browser frameworks" https://pagure.io/fedora-infrastructure/issue/9473#comment-702260 19:03:55 sure. closed upstream or closed insufficent info or something. 19:03:56 ack 19:04:04 thats it on the fedora infra ones... how about releng? 19:04:40 i have an old one to discuss later 19:04:47 ok 19:05:16 * mboddu waits 19:05:22 .ticket 9434 19:05:23 smooge: Issue #9434: DMARC mitigation does not seem working for lists.fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9434 19:05:30 sorry was thinking mboddu had a releng one 19:05:42 np smooge 19:05:44 I am ready to close this one 19:06:15 ok, fine with me. I kept wanting to look closer, but I am pretty sure it's just confusion around how it should work/was working/was configured... and there's nothing really we can do now 19:06:16 I don't think there is much we can do here 19:06:46 it is up to the lists themselves or coming up with a large policy and also dealing with getting a newer mailman out 19:07:00 or moving all our lists to discourse 19:07:10 yep, and people who set 'strict' on their domains... shouldn't. 19:07:26 ok I will also close 9256 19:07:34 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9256 https://pagure.io/fedora-infrastructure/issue/9256 19:07:35 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9256: "Reorganise DNS proxies" https://pagure.io/fedora-infrastructure/issue/9256#comment-702262 19:07:49 releng one's? 19:08:03 ok, wasn't sure that was done but great! 19:08:08 mboddu: fire aways 19:08:12 smooge: I'm slowly getting through updating the mailman stack for Fedora 19:08:23 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9434 https://pagure.io/fedora-infrastructure/issue/9434 19:08:24 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9434: "DMARC mitigation does not seem working for lists.fedoraproject.org" https://pagure.io/fedora-infrastructure/issue/9434#comment-702264 19:08:28 and then we can figure out backporting to EL8 or some other strategy 19:08:42 So, there are no new releng tickets, but I wanna discuss about a ticket/PR 19:08:51 .releng 9856 19:08:53 mboddu: Issue #9856: update epel-release-latest - releng - Pagure.io - https://pagure.io/releng/issue/9856 19:09:03 So, I made the PR https://pagure.io/fedora-infra/ansible/pull-request/316 19:09:35 thanks mboddu 19:09:35 nirik: Good catch on the os.symlink(), I fixed it, but how can we run it only when epel-release build is changed? 19:09:56 I would test if the symlink is broken and then fix :) 19:09:56 By looking on epel-release modification date and if its less than a day... ? 19:10:26 not sure that is possible 19:10:27 smooge: Ahhh, that should fix it, thanks 19:10:28 yeah, we could just test it for brokenness? 19:10:38 * mboddu need to check on that 19:10:38 Eighth_Doctor: thanks again for working on that! 19:10:40 well I mean testing if it was brorken 19:10:49 Anyway, thats all I got 19:11:06 Eighth_Doctor, at this point I am ready to just put mailman3 on fedora and we break/upgrade every 6 months. 19:11:16 that will make my life easier :) 19:11:27 might as well have a firedrill every 6 months that lasts 3 months 19:11:42 well, I don't think it'd go that badly 19:11:56 well this and every other server that needs to be upgraded 19:12:22 but at least getting stuff packaged and working on Fedora is going to be easier up front and then if duck and OSPO wants to help bring it to EL8, then everything will at least be there 19:13:04 because I gave up trying to maintain EL8 compatibility several months ago 19:13:38 I don't have the time to burn for that, and it was hellish getting Mailman 3 shipped in openSUSE to begin with (that's finally done and they've switched over on lists.opensuse.org last week) 19:13:40 understood 19:14:09 anyway.. that is a different ticket. if there isn't one for that, time to put one in for Request for Staging 19:14:11 so, is this one closable: 19:14:19 .ticket 8704 19:14:20 nirik: Issue #8704: Need to backup/copy data from equallogics to storinator - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8704 19:14:26 yeah 19:14:46 did this one get stalled: 19:14:48 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8704 https://pagure.io/fedora-infrastructure/issue/8704 19:14:49 .ticket 9226 19:14:50 nirik: Issue #9226: Relocate Dogtag PKI's four public mailing lists from "www.redhat.com/mailman/listinfo" to "lists.fedorahosted.org" - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9226 19:14:57 it is stalled 19:15:02 I need some help on it 19:15:14 I have no clue how to import lists into mailman3 19:15:21 and I keep getting distracted 19:15:28 ok, we should ask abompard when we catch him around. 19:15:31 so I am going to ask for someone to beat me on it 19:15:45 we just need to close 2 more tickets 19:15:58 this one looks like the one we just closed: 19:16:05 .ticket 9214 19:16:06 nirik: Issue #9214: [GitHub API] Deprecation notice for authentication via URL query parameters - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9214 19:16:35 but duck had a patch here I guess? or possibly ? 19:17:37 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9214 https://pagure.io/fedora-infrastructure/issue/9214 19:17:38 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9214: "[GitHub API] Deprecation notice for authentication via URL query parameters" https://pagure.io/fedora-infrastructure/issue/9214#comment-702268 19:17:43 I am just closing stuff 19:18:53 ok. I didn't have any others. 19:19:01 reminder: I will be out friday and all next week. 19:19:10 (not that I am going anywhere, but...) 19:19:56 I'm hoping to look at those broken staging apps this afternoon and possibly get together with otaylor today/tomorrow to look at the registry ticket. 19:20:29 anyhow, will close in a min if nothing else... 19:21:02 nirik: Updated the PR - https://pagure.io/fedora-infra/ansible/pull-request/316 19:21:58 Hold on a sec before merging 19:22:11 sure, can look in a few. 19:22:14 #endmeeting