19:00:31 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:31 Meeting started Fri Jan 17 19:00:31 2020 UTC. 19:00:31 This meeting is logged and archived in a public location. 19:00:31 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:31 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:31 #chair smooge nirik relrod cverna 19:00:31 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:31 #info agenda is at https://board.net/p/fedora-infra-daily 19:00:31 Current chairs: cverna nirik relrod smooge 19:00:32 #topic Tickets needing review 19:00:33 #info https://pagure.io/fedora-infrastructure/issues 19:01:33 * nirik waves 19:01:36 hello 19:01:41 no tickets need review today 19:01:57 wow. how did that happen? :) 19:02:05 * smooge was looking for emacs tar balls 19:02:27 anyhow, shall we do some waiting on reporters? or call it a quick sync up ? or ? 19:03:02 waiting on reporters 19:03:21 ok 19:03:30 https://pagure.io/fedora-infrastructure/issues?status=Open&priority=4 19:03:45 .ticket 7456 19:03:47 nirik: Issue #7456: erlang group in src.fpo - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7456 19:04:09 * nirik looks to see whats left here. 19:04:38 I think it's all left on bowlofeggs here... 19:04:50 i think there needs to be an email or something from bowlofeggs 19:04:57 oops 19:05:34 Just for info I turned off the Koji nagios wellness plugin I was not sure if that was the reason for the load this morning. We can try putting it back and see what happens. 19:05:35 proposal: close and ask him to let us know if he gets stuck anywhere or needs anything further 19:05:42 +1 19:05:49 cverna: ok, the load went down after that? 19:05:58 smooge: you got it? or shall I? 19:06:08 nirik yes 19:06:26 But I am not 100% sure it was related 19:06:28 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#7456 https://pagure.io/fedora-infrastructure/issue/7456 19:06:29 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#7456: "erlang group in src.fpo" https://pagure.io/fedora-infrastructure/issue/7456#comment-621532 19:06:36 cverna: weird. ok. we can see I guess. last night for me things got unresponsive and db-koji01's load was up to about 400 or so... I had to restart postgresql 19:06:58 .ticket 7685 19:06:59 nirik: Issue #7685: Error 500 when trying to connect to src.fp.o - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7685 19:07:27 * cverna goes back to his Friday evening 19:07:57 night/weekend cverna thanks 19:08:01 night cverna 19:08:14 ok, on this one I am not sure if it's still happening 19:08:14 Have good weekend 🙂 19:08:17 we could ping on it 19:08:35 nirik, I don't think this is waiting on reporter anymore. I can put in a ping and if it is fix or close 19:09:02 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#7685: "Error 500 when trying to connect to src.fp.o" https://pagure.io/fedora-infrastructure/issue/7685#comment-621534 19:09:02 might be waiting on pingou to look again I guess... 19:09:20 .ticket 8218 19:09:21 nirik: Issue #8218: non-critical fedora coreos apps in communishift - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8218 19:10:02 you know we have the best closing rate on these waiting on reporter tickets. What if we put all the rest in this state? 19:10:23 this I guess is waiting for someone to write the script to sync fas groups to openshift projects 19:10:41 wait on assignee? 19:10:49 ha. :) Or just close everything... "sorry, it's a new year, starting with a clean slate!" 19:10:52 yeah 19:11:06 .ticket 8407 19:11:07 nirik: Issue #8407: aws permissions for starting spot instances - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8407 19:11:14 this should be waiting on assignee... 19:11:22 as should 19:11:29 .ticket 8421 19:11:29 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8218 https://pagure.io/fedora-infrastructure/issue/8218 19:11:30 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8218: "non-critical fedora coreos apps in communishift" https://pagure.io/fedora-infrastructure/issue/8218#comment-621535 19:11:32 nirik: Issue #8421: allow `aws-copr` group to deregister its own images - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8421 19:11:55 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8407 https://pagure.io/fedora-infrastructure/issue/8407 19:11:57 perhaps I can ask davdunc about those in brno 19:12:19 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8421 https://pagure.io/fedora-infrastructure/issue/8421 19:13:19 .ticket 8525 19:13:20 nirik: Issue #8525: Can't kinit for stg.fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8525 19:14:01 so, we need to know if this is still happening or not. ;) 19:14:21 so I guess ping on it and leave in wait on reporter? 19:14:36 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8525: "Can't kinit for stg.fedoraproject.org" https://pagure.io/fedora-infrastructure/issue/8525#comment-621539 19:14:48 okok 19:14:51 .ticket 8532 19:14:52 nirik: Issue #8532: Mount fedora_koji_archive02 on composer.stg.phx2.fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8532 19:15:11 i say we look at this after we get back from pto/brno 19:15:15 so I think this will be solved by a koji sync. which I was gonna try and do... I guess I will try and get to it this afternoon. 19:15:29 so, lets close in favor of the koji sync one 19:15:35 ok 19:15:41 what was the ticket for kojisync 19:15:49 or do you have it? 19:15:55 8334 19:16:00 .ticket 8334 19:16:01 nirik: Issue #8334: please sync koji prod to stage - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8334 19:16:41 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8532 https://pagure.io/fedora-infrastructure/issue/8532 19:16:42 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8532: "Mount fedora_koji_archive02 on composer.stg.phx2.fedoraproject.org" https://pagure.io/fedora-infrastructure/issue/8532#comment-621540 19:17:09 I think I can knock out: 19:17:15 .ticket 8527 19:17:16 nirik: Issue #8527: anitya organization move: need permission to create public repository in fedora-infra - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8527 19:17:20 pretty quick here 19:18:21 cool 19:18:37 man we should clean up our github thing someday... lots of people who no longer work on any of our stuff are in there still. 19:19:36 hum, not sure how to do this after all. 19:20:10 .ticket 7667 19:20:11 smooge: Issue #7667: Pushing container build to registry is failing with 500 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7667 19:20:24 nope wrong one 19:20:34 .ticket 7661 19:20:35 smooge: Issue #7661: GeoIP - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7661 19:20:49 wasn't there an email about updating the code recently? 19:21:15 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#8527 https://pagure.io/fedora-infrastructure/issue/8527 19:21:16 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8527: "anitya organization move: need permission to create public repository in fedora-infra" https://pagure.io/fedora-infrastructure/issue/8527#comment-621542 19:21:22 nirik want me to put in a ticket on that? 19:21:42 updating which code? 19:21:46 ticket on which? 19:21:52 nirik, smooge: i'll just close that erlang ticket - i haven't had time to try out the groups, but i have a todo for that and i can reopen the ticket if i have a problem 19:22:09 bowlofeggs, ok 19:22:27 oh it is closed, heh 19:22:32 sorry nirik . open a ticket on cleaning up our github users 19:22:39 smooge: sure! 19:22:49 and updating the geoip code 19:22:55 ideally we would also make sure all the sysadmin-main folks were owners there too 19:23:07 someone had a patch which needed things 19:23:19 I think the patch was on the mailing list? 19:23:23 someone had a patch for the geoip which worked with the newer database.. 19:23:53 yeah. I wasn't sure if it got applied 19:24:23 I don;t think it ever did... so yes, that would be good to follow up on. 19:25:00 so I guess we cancel all these next week right? and possibly mon/tue/wed of following week also? 19:25:10 ok will do so 19:25:21 anything else for this meeting? 19:25:32 don't think so off hand... 19:25:50 ok end of meeting. time to get ready for another meeting 19:25:57 #endmeeting