18:03:50 <phsmoura> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:03:50 <zodbot> Meeting started Tue Sep 27 18:03:50 2022 UTC. 18:03:50 <zodbot> This meeting is logged and archived in a public location. 18:03:50 <zodbot> The chair is phsmoura. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:03:50 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:03:50 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:03:50 <phsmoura> #chair nirik mobrien aheath1992 smooge 18:03:50 <phsmoura> #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:03:50 <phsmoura> #info meeting is 30 minutes MAX. At the end of 30, its stops 18:03:50 <phsmoura> #info agenda is at https://board.net/p/fedora-infra-daily 18:03:51 <zodbot> Current chairs: aheath1992 mobrien nirik phsmoura smooge 18:03:51 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:03:59 <erolkskn> hi there 18:04:01 <nirik> morning 18:04:02 <phsmoura> morning :) 18:04:09 <smooge> mello 18:04:31 <phsmoura> #info reminder: speak up if you want to work on a ticket! 18:04:31 <phsmoura> #topic Tickets needing review 18:04:45 <phsmoura> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:05:25 <phsmoura> .ticket 10918 18:05:26 <zodbot> phsmoura: Issue #10918: Need admin access to the fedora-infra/mdapi repo - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10918 18:05:46 <nirik> med gain low effort ops? 18:05:56 <phsmoura> +1 18:06:52 <phsmoura> .ticket 10919 18:06:53 <zodbot> phsmoura: Issue #10919: Investigate probable spammy account "janicelporto" - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10919 18:07:05 <nirik> low low ops? 18:07:11 <phsmoura> +1 18:07:56 <phsmoura> I can keep in track of that issue if no one start to working on it til tomorrow I can do it 18:08:12 <phsmoura> just need to focus in other stuff now :/ 18:08:30 <nirik> no worries. I can do it, or if I don't get to it, you can do it tomorrow... 18:08:43 <phsmoura> cool 18:09:08 <phsmoura> now is releng time 18:09:16 <phsmoura> #info https://pagure.io/releng/issues?status=Open 18:09:56 <phsmoura> .releng 11052 18:09:57 <zodbot> phsmoura: Issue #11052: A week before the scheduled final freeze, retire F37 FailsToInstall packages - releng - Pagure.io - https://pagure.io/releng/issue/11052 18:10:14 <nirik> low low ops? 18:10:45 <nirik> it's already done mostly anyhow 18:10:59 <phsmoura> ok 18:11:53 <phsmoura> thats is it. lets go to open floor 18:12:16 <phsmoura> just a min I accidently closed my browser :) 18:12:35 <phsmoura> #topic Planning, Upcoming work and Open floor 18:13:29 <erolkskn> Alright, i've been examining the fedbadges stack's source in a while, and i've seen that fedbadges still depends on fedmsg-hub 18:13:41 <phsmoura> Im working on the firmware issue thing and need to do stuff for centos as well. this is basically what Ive been doing 18:13:41 <erolkskn> i'm guessing that there is a service that replicates messages from fedora-messaging to fedmsg-hub ? 18:13:53 <eddiejenningsjr> Looking at current plate outside of work, it's not realistic for me to get up to speed of the fedora planet template stuff and contribute to it :( 18:14:36 <erolkskn> And as a side note, is there any chance that i could get read-only access to fedbadge's machine ? 18:14:39 <nirik> erolkskn: yeah, it does. Also, it's python2 ;( and the backend gets stuck often 18:15:11 <erolkskn> so i can see the logs and better understand what are the problems behind the stuff 18:15:20 <nirik> yes, there is a project/app called 'messaging bridges' that gateways fedmsg/fedora-messaging to each other and verifies that both buses have the same messages. 18:15:36 <nirik> sure, you may already have access as apprentice? 18:16:07 <erolkskn> oh didn't know that fedbadges is open to apprentices, sorry about that 18:16:21 <nirik> there are 2 vm's: 18:16:41 <nirik> badges-web01 thats the frontend and badges-backend01 thats the backend 18:17:02 <phsmoura> eddiejenningsjr: Ive been doing alone had just 1 commit from another contributor and I have other issues with higher priority so dont worry if its taking time to contribute in fedora planet and if you want to look for other thing to work theres no problem as well :) 18:17:23 <erolkskn> btw i had thought that i could replace fedmsg with fedora-messaging in fedbadges project and go on with it, but it seems like it wouldn't solve the issue 18:17:36 <erolkskn> there are a lot of cron jobs that depends on fedmsg 18:17:57 <erolkskn> i should probably refactor them too 18:18:01 <nirik> erolkskn: yeah. I think it may need our fedora-messaging apps to all publish schemas... 18:19:18 <nirik> first thing might be to try and see if you could stablize the backend... it gets stuck and messages pile up and I have just been dumping all those messages and restarting it... since I don't know whats causing the blockage 18:19:57 <erolkskn> it's probably due to the Mutex lock in consumer 18:20:05 <eddiejenningsjr> Yeah. I need to take a step back and better prioritize my outside-of-work time in general 18:20:30 <nirik> I suspect it might be some fedora-messaging message that has something it doesn't understand, so it just stops 18:20:37 <nirik> but I am not sure. 18:20:42 <erolkskn> yeah that could be another reason too 18:20:53 <erolkskn> alright then, if those machines are accessible to me i will read the logs 18:21:20 <erolkskn> and try to get an insight about what's the main problem 18:21:48 <nirik> sounds good. 18:23:36 <erolkskn> nirik: thanks a lot for the information about vms 18:24:42 <nirik> happy to help. 18:24:55 <nirik> #info networking outage later today 18:25:12 <nirik> I have that and trying to catch up. Today has been busy. ;) 18:25:21 <nirik> otherwise, nothing from me... 18:28:15 <phsmoura> nothing else here too 18:28:29 <erolkskn> same here 18:28:32 <phsmoura> thank you all :) 18:28:36 <erolkskn> thank you :) 18:28:41 <phsmoura> #endmeeting