18:00:15 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:16 Meeting started Mon Jun 15 18:00:15 2020 UTC. 18:00:16 This meeting is logged and archived in a public location. 18:00:16 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:16 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:16 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:16 #chair cverna mboddu nirik smooge 18:00:16 Current chairs: cverna mboddu nirik smooge 18:00:16 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:16 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:16 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:16 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:17 #topic Tickets needing review 18:00:18 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:24 hey folks 18:00:28 hello 18:00:31 long time no see 18:00:47 we have 14 tickets in needs review. ;( 18:00:53 .ticket 8989 18:00:55 nirik: Issue #8989: add queued and running as additional supported outcomes to resultsdb - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8989 18:01:16 I will do the data work 18:01:42 this one seems tagged and just needs to move to waiting on assignee? 18:01:45 so, not sure what to do with this. It kinda intertwines with who is upstream for it now 18:02:10 move to waiting on external perhaps and note that until we have an upstream we aren't going to just change things... 18:03:00 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8989 https://pagure.io/fedora-infrastructure/issue/8989 18:03:05 .ticket 8995 18:03:05 nirik: Issue #8995: sssd-docs redirection - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8995 18:03:30 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8989: "add queued and running as additional supported outcomes to resultsdb" https://pagure.io/fedora-infrastructure/issue/8989#comment-658362 18:03:40 just needs someone who can stand apache redirects doing. Proposed: medium-trouble, medium-gain, waitingonasignee? 18:04:07 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8995: groomed, medium-gain, and 2 others https://pagure.io/fedora-infrastructure/issue/8995 18:04:08 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8995 https://pagure.io/fedora-infrastructure/issue/8995 18:04:16 done 18:04:17 .ticket 9000 18:04:18 nirik: Issue #9000: Adjust distgit_check_hook.py to move the pagure hooks - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9000 18:04:33 move to waiting on asignee 18:04:38 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9000 https://pagure.io/fedora-infrastructure/issue/9000 18:05:06 .ticket 9001 18:05:07 nirik: Issue #9001: Port dist-git to fedora-messaging - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9001 18:05:59 I guess move to waiting on asignee... the only thing I could think of is also to check that it can connect to rabbitmq at all? 18:06:16 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9001 https://pagure.io/fedora-infrastructure/issue/9001 18:06:17 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9001: "Port dist-git to fedora-messaging" https://pagure.io/fedora-infrastructure/issue/9001#comment-658365 18:06:58 it is a 10.3.169 host, but did we allow all those to talk to rabbitmq? well, via the proxies 18:07:18 .ticket 9006 18:07:19 nirik: Issue #9006: fedora-alt filelists are empty on dl-iad01 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9006 18:07:30 I fixed this the other day. 18:07:39 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#9006 https://pagure.io/fedora-infrastructure/issue/9006 18:07:40 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9006: "fedora-alt filelists are empty on dl-iad01" https://pagure.io/fedora-infrastructure/issue/9006#comment-658367 18:07:52 .ticket 9007 18:07:53 nirik: Issue #9007: batcave01.iad2 can not reposync el7 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9007 18:08:13 mboddu has a PR there... 18:08:23 I noticed the el6 one was also failing. 18:08:30 yeah they would all fail 18:08:44 smooge: can you look at/merge/push the pr? or want me to? 18:08:47 rebasing and mering 18:08:52 cool. 18:08:57 pagure.pull-request.comment.added -- mohanboddu commented on PR #119 on fedora-infra/ansible https://pagure.io/fedora-infra/ansible/pull-request/119#comment-122877 18:08:59 if it doesn't work I ill do it myself 18:09:03 pagure.pull-request.flag.updated -- Zuul updated the flags on fedora-infra/ansible#119 with: "Jobs result is pending" https://pagure.io/fedora-infra/ansible/pull-request/119 18:09:10 .ticket 9010 18:09:10 pagure.pull-request.comment.added -- smooge commented on PR #119 on fedora-infra/ansible https://pagure.io/fedora-infra/ansible/pull-request/119#comment-122878 18:09:10 nirik: Issue #9010: Authentication failure when trying to use sudo on badges-* - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9010 18:09:30 misc: can you retry this now? it should work... but I moved badges to iad2. 18:09:42 pagure.pull-request.comment.added -- smooge commented on PR #119 on fedora-infra/ansible https://pagure.io/fedora-infra/ansible/pull-request/119#comment-122879 18:09:43 pagure.pull-request.closed -- smooge merged pull request #119 on fedora-infra/ansible https://pagure.io/fedora-infra/ansible/pull-request/119 18:10:04 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#9010 https://pagure.io/fedora-infrastructure/issue/9010 18:10:05 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9010: "Authentication failure when trying to use sudo on badges-*" https://pagure.io/fedora-infrastructure/issue/9010#comment-658369 18:10:13 .ticket 9012 18:10:14 nirik: Issue #9012: Cannot push to pagure.io/docs/odcs.git - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9012 18:10:45 proposed: low-trouble,medium-gain, waiting on assignee 18:10:51 pagure.pull-request.flag.updated -- Zuul updated the flags on fedora-infra/ansible#119 with: "Jobs result is success" https://pagure.io/fedora-infra/ansible/pull-request/119 18:10:53 pagure.pull-request.comment.added -- zuul commented on PR #119 on fedora-infra/ansible https://pagure.io/fedora-infra/ansible/pull-request/119#comment-122880 18:10:55 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9012: groomed, low-trouble, and 2 others https://pagure.io/fedora-infrastructure/issue/9012 18:10:56 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9012 https://pagure.io/fedora-infrastructure/issue/9012 18:11:14 .ticket 9021 18:11:15 nirik: Issue #9021: Move the loopabull tasks to openshift - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9021 18:11:25 proposed: low-trouble,medium-gain, waiting on assignee 18:11:44 .ticket 9023 18:11:45 nirik: Issue #9023: pagure.io user activity 'heat map' does not display (404 for cal-heatmap.source-map.js) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9023 18:12:05 proposed: low-trouble,medium-gain, waiting on assignee? or should we close it in favor of another one... let me look for a min. 18:12:18 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9007: "batcave01.iad2 can not reposync el7" https://pagure.io/fedora-infrastructure/issue/9007#comment-658372 18:12:56 * mboddu is here 18:13:02 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9021: groomed, low-trouble, and medium-gain https://pagure.io/fedora-infrastructure/issue/9021 18:13:03 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#9021 to pingou https://pagure.io/fedora-infrastructure/issue/9021 18:13:04 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9021 https://pagure.io/fedora-infrastructure/issue/9021 18:13:37 I don't see another ticket... but if it's going to be fixed in next release, lets close it upstream and point to that... https://pagure.io/pagure/issue/4891 18:14:09 .ticket 9029 18:14:10 nirik: Issue #9029: btrfs-progs-5.6.1-1.fc33 is stuck in bodhi - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9029 18:14:35 proposal: close->fixed 18:14:47 +1 18:15:00 .ticket 9031 18:15:01 nirik: Issue #9031: review-stats script cronjob timing issue - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9031 18:15:26 nirik, sorry trying to catch up 18:15:41 9021 you mean close as upstream and point to 4891? 18:16:34 yep. 18:16:38 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9023 https://pagure.io/fedora-infrastructure/issue/9023 18:16:39 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9023: "pagure.io user activity 'heat map' does not display (404 for cal-heatmap.source-map.js)" https://pagure.io/fedora-infrastructure/issue/9023#comment-658374 18:16:44 soory, no 18:16:50 9023 18:17:00 yeah.. i fixed it before i did it 18:17:05 cool. 18:17:12 9029 close fix 18:17:21 Yes 18:17:22 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9029 https://pagure.io/fedora-infrastructure/issue/9029 18:17:41 ok back to 9031 18:17:45 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#9031 https://pagure.io/fedora-infrastructure/issue/9031 18:17:46 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9031: "review-stats script cronjob timing issue" https://pagure.io/fedora-infrastructure/issue/9031#comment-658377 18:17:56 fixed. ;) 18:18:03 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9007 https://pagure.io/fedora-infrastructure/issue/9007 18:18:22 with nfs volumes set to Retain, you have to delete the pv and recreate it for it to get used again. 18:18:25 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9031: "review-stats script cronjob timing issue" https://pagure.io/fedora-infrastructure/issue/9031#comment-658380 18:18:30 .ticket 9032 18:18:31 nirik: Issue #9032: inactive accounts should not be listed as package Cc/owner etc. - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9032 18:19:14 proposed: medium-trouble,medium-gain, waiting on assignee? 18:19:43 we might want a script/task that finds all inactive users that have cc/owner and removes them? or perhaps not... 18:19:46 +1, but it seems high-trouble 18:19:59 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9032: authentication, high-trouble, and 2 others https://pagure.io/fedora-infrastructure/issue/9032 18:20:00 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9032 https://pagure.io/fedora-infrastructure/issue/9032 18:20:16 Yeah, I dont know how to handle the situation, hence high trouble 18:20:25 yeah, could be yes. 18:20:31 .ticket 9034 18:20:32 nirik: Issue #9034: publickey denied: automation of doc stg internationalization scripts - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9034 18:20:48 proposed: medium-trouble,medium-gain, groomed waiting on assignee? 18:21:12 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9034: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9034 18:21:13 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9034 https://pagure.io/fedora-infrastructure/issue/9034 18:21:17 +1 18:22:05 ok, thats needs review from infra... any releng ones? or other blockers/issues? I'd also like to discuss the idea of moving this standup to #fedora-meeting... so we can leave this channel clear for issues. 18:23:34 Yes 18:23:45 .releng 9526 18:23:46 mboddu: Issue #9526: Block 7 packages retired couple days ago - releng - Pagure.io - https://pagure.io/releng/issue/9526 18:24:10 from the dc move the big issues right now: getting messaging working from bodhi/rawhide composes, fedora_koji storage, docs syncing sorting 18:24:33 mboddu: this may be broken in the rawhide nightly script? 18:24:37 I need to check what happened to block_retired.py 18:24:41 Yes 18:24:53 medium-trouble, high-gain, groomed? 18:24:57 * nirik bets it's python2. ;) 18:25:02 +1 18:25:08 I think I ported it to py3 18:25:31 ok 18:25:35 .releng 9528 18:25:36 mboddu: Issue #9528: f33-perl side tag for Changes/perl5.32 - releng - Pagure.io - https://pagure.io/releng/issue/9528 18:25:46 low trouble, high gain, groomed? 18:26:39 And thats it, the other two are simple things which i am planning on working on after this meeting and lunch 18:27:02 cool. 18:27:23 any objections to moving to fedora-meeting tomorrow? or should I discuss on list? 18:27:31 anything else before we close out? 18:27:35 * mboddu has no objections 18:27:51 As long as I get a ping, thats all it matters :) 18:28:03 * mboddu sometimes forget about these meetings :( 18:30:19 yeah, easy to. ;) would changing the time help/change anything? 18:30:30 I like them late enough in my day to where fires are known... 18:30:48 I dont mind anytime 18:31:32 If changing I prefer changing to later part of the day since my mornings are generally busy 18:31:35 what's the idea about moving them? 18:31:56 Not to disturb #fedora-admin 18:32:06 pingou: sometimes people come in when we are meeting and try and talk about some issue... 18:32:22 but I guess it doesn't happen that often... 18:33:03 I kinda liked them here, but I'm also on -meeting so I'll likely see them if I'm around 18:33:18 (a pro of being here is that we're sure we're never conflicting w/ another meeting :)) 18:33:44 yeah, thats a worry... especially since these are daily. 18:33:58 ok, lets just meet here tomorrow and discuss on list moving... ;) 18:34:03 thanks for coming everyone 18:34:05 #endmeeting