18:01:27 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:01:27 Meeting started Tue Aug 8 18:01:27 2023 UTC. 18:01:27 This meeting is logged and archived in a public location. 18:01:27 The chair is phsmoura. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:01:27 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:27 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:27 #chair nirik smooge phsmoura 18:01:27 Current chairs: nirik phsmoura smooge 18:01:28 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:01:28 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:01:28 #info agenda is at https://board.net/p/fedora-infra-daily 18:01:28 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:32 morning 18:01:33 .hi 18:01:35 aheath1992: Something blew up, please try again 18:01:38 aheath1992: An error has occurred and has been logged. Please contact this bot's administrator for more information. 18:01:59 .hi 18:02:00 aheath1992: Something blew up, please try again 18:02:03 aheath1992: An error has occurred and has been logged. Please contact this bot's administrator for more information. 18:02:21 well looks like i broke zodbot 18:02:27 weird, did zodbot stop working? 18:02:30 .hi 18:02:31 phsmoura: Something blew up, please try again 18:02:34 phsmoura: An error has occurred and has been logged. Please contact this bot's administrator for more information. 18:03:03 :/ 18:04:12 give me a sec 18:06:05 ah thanks smooge 18:06:05 it will take a bit as it needs to reload some dbs 18:06:05 you should be able to go do other things than .hi 18:06:05 .hi 18:06:05 ah ok 18:06:05 it will probably still blow up or not respond.. it usually takes about 4 minutes for a reload to work 18:06:05 lets continue 18:06:06 sorry, got distracted. 18:06:11 phsmoura: phsmoura 'Pedro Moura' 18:06:17 there its 18:06:27 #info reminder: speak up if you want to work on a ticket! 18:06:27 #topic Tickets needing review 18:06:28 it's a long standing bug 18:07:35 is it related to thhis https://pagure.io/fedora-infrastructure/issue/11306 18:07:37 ? 18:08:10 well, that points to the issue... it's https://github.com/fedora-infra/supybot-fedora/issues/94 18:08:39 I tryed to provision vm locally and see how it works but vagrant seems outdated and throws errors when provisioning 18:09:04 so got back to planet.. will give more details in openfloor 18:09:19 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:09:29 we dont have new issue in infra 18:09:46 #info https://pagure.io/releng/issues?status=Open 18:09:59 .releng 11600 18:10:00 phsmoura: Issue #11600: rpms/pew: Delete 2 custom branches - releng - Pagure.io - https://pagure.io/releng/issue/11600 18:10:14 low low ops 18:10:24 +1 18:10:52 .releng 11601 18:10:53 phsmoura: Issue #11601: Branch request can race with repo creation - releng - Pagure.io - https://pagure.io/releng/issue/11601 18:11:36 I didnt understand this one 18:13:23 I'm not sure what we can do about this, but perhaps we will come up with an idea... 18:13:25 med med ops? 18:13:49 +1 18:14:20 basically it's something where the toddler is trying to do things too fast. 18:14:27 (I think) 18:15:02 .releng 11602 18:15:03 phsmoura: Issue #11602: Please Untag golang-opentelemetry-otel-1.16.0-3.fc39 urgently - releng - Pagure.io - https://pagure.io/releng/issue/11602 18:15:34 I can do this after branching is over. 18:15:38 med med ops I guess? 18:16:22 done 18:16:46 #topic Planning, Upcoming work and Open floor 18:17:37 Trying to get the awx and receptor RPMs built and reviewed so we can get them added to the AWX instance 18:17:48 we got hit with a denial of service yesterday afternoon and that sucked up all my time. ;( 18:17:55 I'm trying to catch up today 18:18:14 Seems that I found my mistake in free ipa so reset my commit and doing again to fix the error in noggin 18:19:18 cool. On the vagrant stuff I think ryan was trying to fix it... but others were having problems with it too. 18:20:07 talked to him, he couldnt isolate the issue as well :/ 18:20:38 but Ill work on this again after testing my changes in free ipa 18:21:12 bummer. ;( abompard is back now too, he might be able to find it... 18:21:52 he also sent me a msg hes looking at it :) 18:22:25 ah you mean the vagrant issue? 18:22:56 yeah... but I guess either. ;) 18:23:25 ah cool :) 18:24:07 will contact him again 18:24:17 anything else? 18:24:39 nirik, i may ping you for a package review request a bit later 18:26:27 aheath1992: sure, I still am slogging thru email, so I will answer your email sometime today. ;) 18:26:39 no worries 18:27:54 good luck nirik 18:28:28 thanks, I'll take it. 18:28:51 seems thats all 18:29:01 thanks everyone :) 18:29:10 #endmeeting