19:00:41 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
19:00:41 <zodbot> Meeting started Mon Jan 24 19:00:41 2022 UTC.
19:00:41 <zodbot> This meeting is logged and archived in a public location.
19:00:41 <zodbot> The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
19:00:41 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:41 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
19:00:41 <nirik> #chair mboddu nirik pingou mobrien nb
19:00:41 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
19:00:41 <zodbot> Current chairs: mboddu mobrien nb nirik pingou
19:00:41 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
19:00:41 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
19:00:41 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
19:00:41 <nirik> #info reminder: speak up if you want to work on a ticket!
19:00:43 <nirik> #topic Tickets needing review
19:00:45 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
19:01:20 <phsmoura> hello
19:02:20 <mboddu> Hello
19:02:33 <copperi[m]> hello
19:02:44 <phsmoura> welcome back mboddu
19:02:53 <mboddu> Good to be back phsmoura
19:02:56 <nirik> morning all, just a sec... finishing something up.
19:03:02 <nirik> hope you had a good time away mboddu
19:03:14 <mboddu> nirik: Yeah, it was fun
19:03:48 <mboddu> Each island is soo different
19:04:31 <nirik> .ticket 10493
19:04:32 <zodbot> nirik: Issue #10493: Cannot find relevant tags - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10493
19:04:40 * nirik waits for pagure.
19:04:50 <mobrien> Welcome back mboddu
19:04:55 <mboddu> Thanks mobrien
19:05:01 <mobrien> Hi everyone else
19:05:08 <nirik> ah this. I think it's now fixed? jednorozec fixed the tags on them I thought? or are there still more...
19:05:35 <nirik> Sat Jan 22 18:00:35 2022 rapidjson-1.1.0-18.el9 tagged into epel9-testing by bodhi [still active]
19:05:40 <nirik> yeah, it's fixed now.
19:05:43 <nirik> will close it
19:05:44 <mboddu> It seems fixed
19:05:47 <mboddu> ack
19:06:25 <nirik> .ticket 10494
19:06:26 <zodbot> nirik: Issue #10494: Planned Outage - bodhi.fedoraproject.org - 2022-01-26 12:00 UTC - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10494
19:06:34 <nirik> med med ops outage?
19:06:37 <mboddu> +1
19:06:40 <mboddu> I can mod the tickets
19:07:03 <mboddu> Done
19:07:37 <nirik> ok, cool.
19:07:49 <nirik> .ticket 10495
19:07:50 <zodbot> nirik: Issue #10495: Create gitlab.com/fedora subgroup for source-git repositories - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10495
19:07:56 <nirik> low low ops, just needs doing
19:08:12 <nirik> .ticket 10496
19:08:14 <zodbot> nirik: Issue #10496: New member to the github infra organization - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10496
19:08:19 <mboddu> Is there any proposal on #10495?
19:08:29 <nirik> who is this phsmoura person... ;) I can do this now...
19:08:42 <nirik> mboddu: [11:07:56] <nirik> low low ops, just needs doing ?
19:08:45 <phsmoura> nirik: Thanks :)
19:09:09 <mboddu> nirik: Yeah, on the gitlab source-git group?
19:10:11 <nirik> yeah, thats what that was for... do you disagree/want to discuss more about it?
19:10:46 <mboddu> nirik: Yeah, I wanna know more about it
19:11:13 <nirik> well, this is just a proof of concept type thing from my understanding. They want to see how it could be done.
19:11:18 <mboddu> Its not like I disagree with it, but I wanna know the details of how they plan on using those repos
19:11:47 <nirik> " we just want to start prototyping "
19:12:18 <mboddu> Okay, I can ask in the ticket
19:12:23 <nirik> https://pagure.io/fedora-source-git/sig/issue/1#comment-765283 has a lot more
19:12:28 <mboddu> But I marked it as low, low, ops
19:13:20 <nirik> thats it for infra ones...
19:13:32 <mboddu> I have 3 for releng
19:14:17 <mboddu> .releng 10583
19:14:18 <zodbot> mboddu: Issue #10583: Cannot find relevant tag None of ['epel9-testing', 'epel9-testing-pending'] are in - releng - Pagure.io - https://pagure.io/releng/issue/10583
19:14:36 <mboddu> Seems like jednorozec fixed them, but we need to wait for the push, for now, I will mark it med, med, ops
19:15:10 <nirik> ok. I think it's fixed indeed.
19:15:42 <mboddu> .releng 10585
19:15:44 <zodbot> mboddu: Issue #10585: Stalled EPEL package: NetworkManager-fortisslvpn - releng - Pagure.io - https://pagure.io/releng/issue/10585
19:15:49 <mboddu> low, low, ops
19:16:19 <mboddu> .releng 10587
19:16:20 <zodbot> mboddu: Issue #10587: Stalled EPEL package: libtomcrypt - releng - Pagure.io - https://pagure.io/releng/issue/10587
19:16:25 <mboddu> Same, low, low, ops
19:16:42 <mboddu> That is all for releng
19:16:43 <nirik> +1
19:16:44 <nirik> +1
19:16:57 <nirik> cool.
19:17:05 <nirik> #topic Planning / Upcoming work
19:17:19 <nirik> So, I am starting to get caught up from the holidays finally now.
19:17:34 <mboddu> Go through the emails and still have to caught up on things :)
19:18:39 <nirik> On my plate this week: get power9 boxes up in iad2, want to look at docs phsmoura wrote up for builders, finish building my riscv machine here, and general tickets and meetings and such
19:19:04 <mboddu> "finish building my riscv machine here" where did you order the parts?
19:19:48 <phsmoura> yeah, I just started. My PR is a WIP, but no worries we talk when you have time nirik
19:20:28 <nirik> mboddu: I got a board via some internal folks... and ordered the rest on the net. I just need to assembe and install now.
19:20:35 <nirik> phsmoura: ok, cool.
19:20:45 <nirik> #topic Discussion items / AOB
19:20:48 <nirik> anything to discuss?
19:20:59 <mboddu> nirik: Interesting, I want to build one too, but I am not sure where to get the parts (or trusted place)
19:21:02 <mboddu> Nothing from me
19:22:16 <phsmoura> Nothing here too
19:22:27 <nirik> well, all the parts are pretty normal pc stuff... it's the board thats different/difficult. I hope there's gonna be some much nicer machines later this year too...
19:22:35 <nirik> but we will see.
19:23:11 <nirik> ok, if nothing else will close on out in a  min
19:23:15 <mboddu> Fingers crossed...
19:23:25 <phsmoura> just a question
19:23:35 <phsmoura> I saw the mass rebuild failed
19:23:39 <phsmoura> some pkgs
19:23:49 <mboddu> phsmoura: We are rebuilding them
19:23:56 <phsmoura> so.. whats next?
19:24:19 <mboddu> If everything went fine, we merge the builds back into rawhide tag and file ftbfs (failed to build from source)
19:24:43 <nirik> yeah, all those ones that fail need fixing, but from maintainers, not us
19:24:58 <mboddu> But this time, its a bit different as there were issue with rubygem and ghc macros, so we resubmitted the failed tasks after fixing those macros
19:25:50 <mboddu> Once the resubmitted tasks are done, then it would be merging the builds...
19:26:05 <phsmoura> mboddu: but not same scripts run right?
19:26:37 <mboddu> phsmoura: Nope, they are all different and the re-submission is a one off thing
19:27:03 <phsmoura> Im curious how you automate that for all pkgs that failed once
19:27:48 <nirik> jednorozec scripted it. But basically just gather all the ones that failed after X time and then just 'koji resubmit tasknumber'
19:28:17 <mboddu> phsmoura: Grab the list of failed tasks (CLI/python api) and then loop over the tasks with `koji resubmit <task_id>` thats its
19:29:16 <jednorozec> phsmoura, I did this https://paste.centos.org/view/26e8128e
19:29:41 <phsmoura> Ah ok thanks :) And is it expect when we do mass rebuilds?
19:29:58 <phsmoura> expected**
19:30:00 <jednorozec> this is the better way koji list-tasks --user=releng  --after=2022/01/19 --all --method=build
19:30:05 <jednorozec> just awk that output
19:30:12 <jednorozec> but I ha dproblem with that
19:30:18 <jednorozec> it timeouted on me couple of times
19:30:48 <jednorozec> phsmoura, not really. This was a bug in rpm macros
19:31:33 <nirik> well, it's happened the last few times... I bet it becomes pretty standard.
19:31:56 <mboddu> nirik: Dont say it... ;)
19:32:16 * nirik shrugs, it's not that much trouble really
19:32:38 <jednorozec> no its not
19:32:58 <jednorozec> but it is always better not to do it :D
19:33:05 <mboddu> nirik: Its not the work, its the waste of time
19:33:13 <jednorozec> that.
19:33:30 <nirik> last time I think it was s390x issues that we had to rebuild failures for, before that it was some toolchain issue that we needed to rebuild stuff again for, etc.
19:33:37 <nirik> sure.
19:33:54 <nirik> anyhow, we are over time, will close out and let everyone get back to their wonderfull monday. ;)
19:33:59 <nirik> #endmeeting