19:00:01 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:01 Meeting started Mon Feb 22 19:00:01 2021 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 #info reminder: speak up if you want to work on a ticket! 19:00:04 #topic Tickets needing review 19:00:06 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:01:02 oh boy, a pile... 19:01:10 smooge: you here to mod tickets? 19:01:17 or want me to today? 19:01:22 i am here 19:01:24 and modding 19:01:37 .ticket 9287 19:01:39 nirik: Issue #9287: Fail to log-in to aws using FAS - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9287 19:02:24 authentication med/med ops 19:02:27 I am not sure what to do here. 19:02:33 well, we thought it was an upstream issue. 19:02:44 I don't think there's anything for us to actually do here? 19:03:06 well deploy the new authentication tools 19:03:19 ipsilon as a vm versus pod 19:03:21 ipsilon isn't changing 19:03:32 well, sure, but not sure why that would matter for this. 19:03:37 by then I am not sure what causes it. 19:03:42 then can't fix/won't fix? 19:04:31 sure, and if they see it again, file upstream? and we can help try and gather logs 19:04:52 * linuxmodder lurking 19:06:23 Well, now that I am here, we can releng one's 19:06:29 * mboddu haven't looked at them 19:06:50 ok ticket modded.. onto the next one 19:06:59 .ticket 9680 19:07:00 nirik: Issue #9680: Share Personal Health Dashboard to Fedora CI - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9680 19:07:11 I am not sure the ask here... it doesn't really make sense, so I asked about it. 19:07:17 I guess low/low/ops for now? 19:07:48 done 19:08:07 .ticket 9681 19:08:08 nirik: Issue #9681: Install Openshift on AWS for Fedora CI - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9681 19:08:23 this needs some more investigation. I guess med/med/ops for now. 19:08:50 done 19:08:55 .ticket 9682 19:09:00 close -> won'tfix 19:09:05 nirik: Issue #9682: Datagrepper is not logging events from the FAS account - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9682 19:09:16 done 19:09:21 could mention that stg is down for now as issues with the sync are worked out 19:09:34 .ticket 9684 19:09:35 nirik: Issue #9684: Add zodbot to #fedora-meeting - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9684 19:09:54 close -> done? I think nb added folks... 19:09:58 done 19:10:33 .ticket 9685 19:10:34 nirik: Issue #9685: Bring back mailman in staging - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9685 19:10:46 this is likely a major project 19:11:02 it needs to be done.. but it isn't a quick thing 19:11:05 yeah, might be not at all easy... but mobrien's pr should at least setup the instance 19:11:19 low gain/high trouble/ops? 19:11:50 high gain for me.. we can't duplicate/fix our 'working' mailman until this done 19:12:40 well, if we were deploying the up to date one then it would be more vaulable to me. 19:12:44 but sure 19:12:52 we can't deploy the old one either 19:13:00 that is why it is high-trouble 19:13:23 that was the problem I was running into getting a replacement/backup for the mailman 19:13:35 I know, but if we go to all the trouble, it would be at least nice to have the up to date thing instead of the old crape broken one 19:13:52 so i think the only way is to deploy a new one 19:14:11 right. which is blocked on packaging work. ;( 19:14:27 anyhow, thats the last infra one. 19:14:40 there are 2 more on my window? 19:14:40 and we are up to 82 issues. ;( 19:15:00 .ticket 9686 19:15:00 smooge: Issue #9686: add f34 and f35 (and probably all the way up through f39 because why not) to "old" mirror stats tools - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9686 19:15:10 oh, sorry missed that one 19:15:15 med/med/ops? 19:15:18 that is a me thing 19:15:57 there's also a new one 19:16:03 .ticket 9687 19:16:04 nirik: Issue #9687: Add git bot - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9687 19:16:19 low/low/ops... I can do it sometime 19:17:15 done 19:17:28 on releng side... mboddu: you are off... go do something fun. ;) 19:17:36 .releng 10033 19:17:37 nirik: Issue #10033: Delete created branches - releng - Pagure.io - https://pagure.io/releng/issue/10033 19:17:43 low/low/ops 19:18:19 nirik: If you say so... :) 19:18:20 done 19:18:22 .releng 10034 19:18:23 nirik: Issue #10034: package golang-github-prometheus-node-exporter not in list for tag X-updates-candidate - releng - Pagure.io - https://pagure.io/releng/issue/10034 19:18:37 med/med/ops? not sure how the sync script failed... 19:18:41 But I have couple of things for open floor 19:19:26 dibe 19:19:45 thats all releng side I see... 19:19:55 #topic blockers / prs / discussion 19:20:22 anything to discuss? mboddu you want to bring up your things now? 19:21:01 nirik: Yeah, we need to look at the toddler for updating pdc when a package is retired, esp for f34, I dont seem to find the logs for it in the openshift 19:21:17 I got the access to the project, but I dont find any logs 19:22:03 which toddler is that? but we may need to ask pingou 19:22:46 * mboddu finding it 19:23:00 https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/pdc_retired_packages.py 19:24:38 are those seperate cron jobs? I don't see one named that 19:25:15 oh, I see, it's in the main thing 19:25:27 Nope, its not a cron job, its listen to fedora messages 19:26:04 seems running 19:26:06 2021-02-22 19:22:41,633 - [INFO toddlers.runner] Toddler 'pdc_retired_packages' accepted to process message id: 178e 19:26:07 a5a8-c5f4-4ff9-98f7-3e223ff19277 19:26:07 2021-02-22 19:22:41,638 - [INFO toddlers.plugins.pdc_retired_packages] No dead.package in the commit, bailing 19:26:28 Hmmm, its happening only on F34 19:26:31 Where are the logs? 19:27:36 I am looking in the pod logs via command line: 19:27:39 oc logs pod/toddlers-111-vpzhd | less 19:27:46 (but there's 2 other pods too) 19:28:44 anyhow, what else did you have? we are nearly out of time 19:29:15 I forgot the other one :D 19:29:28 Oh, tomorrow is Bodhi activation point 19:29:54 That is all I got 19:31:34 #topic upcoming work 19:31:43 #info bodhi activation point tomorrow 19:31:49 #info beta freeze tomorrow 19:32:27 I'm going to try and work on tickets this week... see if we cna slay a few. 19:32:44 anything else before we close out? 19:32:57 Nope 19:34:42 #endmeeting