18:00:02 <smooge> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:02 <zodbot> Meeting started Tue May 5 18:00:02 2020 UTC. 18:00:02 <zodbot> This meeting is logged and archived in a public location. 18:00:02 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:02 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:02 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:03 <smooge> #chair cverna mboddu nirik smooge 18:00:03 <smooge> #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:03 <smooge> #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:03 <zodbot> Current chairs: cverna mboddu nirik smooge 18:00:03 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:03 <smooge> #info agenda is at https://board.net/p/fedora-infra-daily 18:00:04 <smooge> #topic Tickets needing review 18:00:05 <smooge> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:11 <smooge> Hello 18:00:30 * nirik had to delete his already pasted ready to hit return version 18:00:49 <nirik> perhaps we should rotate who runs each of these too? 18:00:54 <smooge> yeah.. sorry 18:01:03 <nirik> no biggie. 18:01:08 <nirik> .ticket 8890 18:01:09 <zodbot> nirik: Issue #8890: AWS missing permissions for Testing Farm - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8890 18:01:12 <smooge> I never know if I am late or early so I usually am deleting mine also 18:01:33 <nirik> going to work on this later today... move to waiting on asignee, medium-gain, high-trouble, groomed? 18:02:14 <smooge> ok 18:02:23 <nirik> .ticket 8891 18:02:24 <zodbot> nirik: Issue #8891: github.com/fedora-infra/mbbox webhook perms - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8891 18:02:43 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8890: aws, groomed, and 2 others https://pagure.io/fedora-infrastructure/issue/8890 18:02:44 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8890 https://pagure.io/fedora-infrastructure/issue/8890 18:02:56 <nirik> not sure if this was done, or isn't working. I added a comment there. I guess move to waiting on asignee, medium-gain, medium-trouble, groomed? 18:03:24 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8891: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/8891 18:03:25 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8891 https://pagure.io/fedora-infrastructure/issue/8891 18:03:31 <smooge> done 18:04:06 <nirik> .ticket 8892 18:04:07 <zodbot> nirik: Issue #8892: Side tag update not pushed to testing after 4 days - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8892 18:04:35 <nirik> just looking at this one I think we need cverna. MOve to waiting on asignee, medium/medium, groomed 18:04:50 <smooge> so one thing I think we may need to ask to be added to pagure is a way to move tickets which have been closed and reopened to need-review 18:05:14 <nirik> we can... just change it to needs-review. ;) 18:05:20 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8892: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/8892 18:05:21 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8892 https://pagure.io/fedora-infrastructure/issue/8892 18:06:16 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8892: "Side tag update not pushed to testing after 4 days" https://pagure.io/fedora-infrastructure/issue/8892#comment-650530 18:06:26 <nirik> .ticket 8893 18:06:26 <smooge> nirik, I saw a couple of tickets reopened this last week and I am expecting they will get worked/looked at later than if they were done automagically 18:06:28 <zodbot> nirik: Issue #8893: s390x Koji builders seem broken - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8893 18:06:49 <nirik> smooge: I did that for one ticket over the weekend, we talked about it in yesterdays standup. ;) 18:07:05 <nirik> I am going to close this one in favor of the existing koji one. 18:07:23 <smooge> treis to figure out if s390 should be labeled koji or mt-doom 18:07:40 <smooge> ok 18:07:46 <fm-admin> pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#8893 https://pagure.io/fedora-infrastructure/issue/8893 18:07:47 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8893: "s390x Koji builders seem broken" https://pagure.io/fedora-infrastructure/issue/8893#comment-650532 18:08:44 <nirik> thats all needs reviews. 18:08:49 <mboddu> I have one 18:09:02 <mboddu> I can go now or after dc update 18:09:12 <nirik> go ahead 18:09:23 <mboddu> .releng 9437 18:09:24 <zodbot> mboddu: Issue #9437: Need to retag gdb-9.1-4.fc32 from "trashcan" to some other tag - releng - Pagure.io - https://pagure.io/releng/issue/9437 18:09:48 <mboddu> Can we tag it back to f32-updates-candidate? Or they have to rebuild it? 18:10:05 <mboddu> For some reason they didn't submit the update and now its tagged for gc 18:11:22 <nirik> yep. 18:11:34 <nirik> as long as it's not deleted, you can tag it back and untag trashcan 18:12:29 <nirik> in fact, they could tag it back to candidate, but not sure they can remove trashcan 18:12:35 <nirik> anyhow, just needs doing. :) 18:12:37 <mboddu> nirik: Yeah, I checked and it got deleted? Hence the question 18:13:00 <mboddu> If we tag it back to candidate tag, does koji can do this automagically? 18:13:07 <mboddu> Or is it gone forever? 18:13:17 <nb> if it is deleted, i think they have to bump n-v-r and rebuild 18:13:42 <mboddu> Okay, thanks nb 18:13:47 <nirik> if it's deleted it's gone forever and ever 18:14:04 <mboddu> Thanks 18:14:07 <mboddu> Thats all I got 18:14:45 <nirik> it looks for untagged things not used in any buildroots, tags them trashcan for (30days? something) and then deletes them... that gives a time like this to notice they should be back 18:15:26 <fm-admin> pagure.issue.comment.added -- praiskup commented on ticket fedora-infrastructure#8842: "Give the channel OP on #buildsys-build for "copr" pagure.io group" https://pagure.io/fedora-infrastructure/issue/8842#comment-650538 18:15:32 <nirik> Not much new on dc front. We have a bunch more mgmt interfaces configured now. Just rounding up the scragglers... 18:15:41 <nirik> soon hopefully we will get a virthost installed. 18:16:13 <nb> nirik, I'll take 8842 18:16:18 * nb can contact spot 18:16:31 <fm-admin> pagure.issue.assigned.added -- nb assigned ticket fedora-infrastructure#8842 to nb https://pagure.io/fedora-infrastructure/issue/8842 18:16:50 <nirik> nb: ok, thanks! 18:17:40 <nirik> if we could do that OIDC request today that would be nice. 18:17:51 <nirik> anyone have any other tickets or issues or reviews they need? 18:20:50 <fm-admin> pagure.issue.comment.added -- nb commented on ticket fedora-infrastructure#8842: "Give the channel OP on #buildsys-build for "copr" pagure.io group" https://pagure.io/fedora-infrastructure/issue/8842#comment-650545 18:21:14 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8842: "Give the channel OP on #buildsys-build for "copr" pagure.io group" https://pagure.io/fedora-infrastructure/issue/8842#comment-650546 18:21:42 <nirik> ok, thanks everyone. 18:21:46 <nirik> see you tomorrow at the same time 18:21:49 <nirik> #endmeeting