18:04:09 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:04:09 Meeting started Tue Apr 21 18:04:09 2020 UTC. 18:04:09 This meeting is logged and archived in a public location. 18:04:09 The chair is cverna. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:04:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:04:09 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:04:09 #chair cverna mboddu nirik smooge 18:04:09 Current chairs: cverna mboddu nirik smooge 18:04:14 .hello mohanboddu 18:04:15 mboddu: mohanboddu 'Mohan Boddu' 18:04:19 thanks.. couldn't find them myself 18:04:19 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:04:19 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:04:20 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:04:20 I was waiting for board to load. ;) slow from here 18:04:31 #info agenda is at https://board.net/p/fedora-infra-daily 18:04:31 #topic Tickets needing review 18:04:31 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:04:44 Nothing from releng side 18:04:50 .ticket 8846 18:04:51 nirik: Issue #8846: FedoraMessaging is missing messages - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8846 18:04:57 yeah it took a few minutes to load here too 18:05:11 I guess this one just needs more back and forth? 18:05:29 I think abompard and mkonecny are helping with this one, so we can move to waiting assignee 18:05:38 +1 18:05:39 pagure.issue.edit -- cverna edited the priority fields of ticket fedora-infrastructure#8846 https://pagure.io/fedora-infrastructure/issue/8846 18:05:48 .ticket 8847 18:05:49 nirik: Issue #8847: Change fedora-docs build frequence - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8847 18:06:11 just needs doing... waiting on assignee, low-trouble, medium-gain? 18:06:16 Sorry, I do have one 18:06:23 and do we want to add 'groomed' ? 18:06:24 But, we can get to it later 18:06:31 yeah it will need to have a FBR ? 18:06:41 yep. for prod it will. 18:06:49 pagure.issue.tag.added -- cverna tagged ticket fedora-infrastructure#8847: low-trouble and medium-gain https://pagure.io/fedora-infrastructure/issue/8847 18:06:50 .ticket 8848 18:06:50 pagure.issue.edit -- cverna edited the priority fields of ticket fedora-infrastructure#8847 https://pagure.io/fedora-infrastructure/issue/8847 18:06:51 nirik: Issue #8848: Blog no longer listed on planet - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8848 18:07:04 this one ditto. just needs looking at. No freeze needed tho. ;) 18:07:37 pagure.issue.tag.added -- cverna tagged ticket fedora-infrastructure#8848: low-trouble and medium-gain https://pagure.io/fedora-infrastructure/issue/8848 18:07:38 pagure.issue.edit -- cverna edited the priority fields of ticket fedora-infrastructure#8848 https://pagure.io/fedora-infrastructure/issue/8848 18:07:47 thats all the needs-reviews. 18:07:51 mboddu: you have one? 18:07:57 this seems to happen every now and then, do we know the root cause ? 18:07:59 nirik: Yes 18:08:06 .releng 9413 18:08:07 mboddu: Issue #9413: Build possibly running into aarch64 kernel panic - releng - Pagure.io - https://pagure.io/releng/issue/9413 18:08:29 cverna: I don't think this is it being hung. It's something different... 18:08:58 nirik: ok 18:09:03 mboddu: so, I think thats not a kernel panic... I think it's OOMing killing kojid. 18:09:17 pagure.issue.tag.added -- cverna tagged ticket fedora-infrastructure#8847: groomed https://pagure.io/fedora-infrastructure/issue/8847 18:09:26 nirik: Yeah, I haven't checked the builder yet 18:09:45 but I could be wrong. 18:09:48 But there are bunch of buildroots attached to it 18:10:01 Which means, either it got resubmitted by the user or automatically 18:10:02 yeah, typically thats when kojid gets killed, so it restarts again... 18:10:34 But if the task is restarted, wont it pick random builder 18:10:35 so, I think this just needs investigation... 18:10:48 pagure.issue.assigned.added -- cverna assigned ticket fedora-infrastructure#8846 to abompard https://pagure.io/fedora-infrastructure/issue/8846 18:10:49 pagure.issue.comment.added -- cverna commented on ticket fedora-infrastructure#8846: "FedoraMessaging is missing messages" https://pagure.io/fedora-infrastructure/issue/8846#comment-643413 18:10:50 sure... 18:10:59 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8848 to smooge https://pagure.io/fedora-infrastructure/issue/8848 18:11:18 Meaning, OOM might not be the problem, but yes, it needs investigation 18:12:09 Thats all I got 18:12:10 what makes you think it didn't use different builders? 18:12:36 it definitely did. ;) click on those buildroots. 18:13:54 Yeah 18:14:02 ok, so any other blockers or reviews pending or tickets to talk about? 18:14:20 did we want to adjust tickets for our dashboard? 18:15:15 +1 18:15:28 I created the groomed tag in fedora-infra 18:15:42 I created groomed tag in releng as well 18:15:43 so, I think the big one would be to unassign everyone from things that they are not working on right now. 18:15:56 oh, I just saw a flaw... you can't do that in bugzilla right? 18:15:59 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8848: "Blog no longer listed on planet" https://pagure.io/fedora-infrastructure/issue/8848#comment-643418 18:16:20 bz will be handled differently anyway 18:16:30 So, we can tweak around bz however we want 18:16:32 ha yeah bugzilla assigns it to you by default 18:16:37 how will we know when they are in progress? 18:16:58 there is a status in bugzilla "ASSIGNED" ? 18:17:19 yeah, we can use that 18:17:49 we can open a ticket on tbs to support that 18:18:09 can we move the in-progress stuff to the top and groomed below that and the rest below that? 18:18:10 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8835: "snapshot epel7 as a point release archive" https://pagure.io/fedora-infrastructure/issue/8835#comment-643419 18:18:28 it seems weird to me to see the planned ones first when you look and thats by far the not most important part 18:18:40 pagure.issue.assigned.reset -- cverna reset the assignee of ticket fedora-infrastructure#8507 https://pagure.io/fedora-infrastructure/issue/8507 18:18:41 sure. I can open some tickets. :) 18:19:00 for anyone following (or trying to) we are talking about: https://fedora-infra.github.io/tbs/ 18:19:45 yeah I think it makes sense to have one big column with in progress first, then groomed and then the remaining billions of tickets :D 18:20:50 ok, can file tickets and see what people think. 18:20:57 anything else we need to talk about today? 18:22:32 pagure.issue.comment.added -- tdawson commented on ticket fedora-infrastructure#8835: "snapshot epel7 as a point release archive" https://pagure.io/fedora-infrastructure/issue/8835#comment-643423 18:23:22 I am good :) 18:23:51 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8848 https://pagure.io/fedora-infrastructure/issue/8848 18:23:52 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8848: "Blog no longer listed on planet" https://pagure.io/fedora-infrastructure/issue/8848#comment-643424 18:24:12 Nothing from me 18:24:56 #endmeeting