18:00:36 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:36 Meeting started Mon Mar 9 18:00:36 2020 UTC. 18:00:36 This meeting is logged and archived in a public location. 18:00:36 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:36 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:36 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:36 #chair cverna mboddu nirik smooge 18:00:36 Current chairs: cverna mboddu nirik smooge 18:00:36 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:36 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:37 #topic Tickets needing review 18:00:38 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:48 .hello mohanboddu 18:00:50 mboddu: mohanboddu 'Mohan Boddu' 18:00:55 we did not move this to UTC 18:00:57 .ticket 8729 18:00:58 nirik: Issue #8729: Do we want to have a copy of translate.fp.o backups? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8729 18:01:15 not that I know of... lets do tickets and then talk about it. 18:01:30 on this one, I would say 'yes'. So move to waiting on asignee 18:01:36 and someone needs to figure out what we have to do. 18:01:51 next ticket is private marked. 18:02:06 smooge: did you want to do that one? or should I just do it? 18:02:10 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8729 https://pagure.io/fedora-infrastructure/issue/8729 18:02:12 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8729: "Do we want to have a copy of translate.fp.o backups?" https://pagure.io/fedora-infrastructure/issue/8729#comment-631781 18:02:22 I was going to do the next one 18:02:28 thanks for the reminder 18:02:44 I started at 07:00 local and got sidetracked 18:03:00 no worries. hit me if you need info on how to. 18:03:08 .ticket 8731 18:03:09 nirik: Issue #8731: s390x builders don't set proper hostname into the BuildHost tag in rpms - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8731 18:03:20 you put it in a different ticket so I was going to find that and do so 18:03:40 what dns servers do the s390 builders use? 18:03:41 I am not sure what we want to do with this one yet... I guess move it to waiting on external. 18:03:47 do they call 10.5.126.21? 18:04:18 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8731 https://pagure.io/fedora-infrastructure/issue/8731 18:04:30 I think yeah, ours... 18:04:37 if they call the phx2 dns then I can just put ina reverse zone for them 18:04:38 but I question the use of that information 18:05:06 I will follow whatever releng wants to do 18:05:28 I know people use that info for various reasons... but no idea why 18:05:33 pagure.issue.new -- sumantrom opened a new ticket fedora-infrastructure#8732: "Yubi Key test renders 500" https://pagure.io/fedora-infrastructure/issue/8732 18:05:39 damnit 18:06:13 .ticket 8732 18:06:14 smooge: Issue #8732: Yubi Key test renders 500 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8732 18:06:15 yeah, In general I hate tickets that are just discussion... :) but lets leave that one around and we can deal with it when we know more 18:06:36 the dangit was that we got a ticket added 18:06:43 I was helping Sumantro with this 18:07:18 I built a new python-yubico package 18:07:18 so, what do they need to access? 18:08:32 They are not accessing anything, in https://admin.fedoraproject.org/accounts/yubikey/, when they tried test auth, its returning 500 for them 18:08:56 yeah, something in the bowells of fas. 18:09:37 We need to fix this asap, since the new yubikey registrations is not going to work with current python-yubico package 18:09:59 But I dont know if the issue is in new python-yubico package that I built or something in our infra 18:12:11 (side note, the new python-yubico build also has a issue, I hotfixed it to burn the key in sumantro's laptop, which I need to apply the patch and build) 18:12:11 ok, so move to waitng on assignee and someone will have to dig into logs. 18:12:31 but do note this affects a very small number of people... sysadmins who have sudo somewhere. 18:12:50 Right 18:14:53 * nirik found a traceback. can add to the ticket 18:14:59 ok, thats all the needs infos... 18:15:18 Do we want to move this standup time? I think it's fine, but willing to move 18:15:29 I have a ticket 18:16:03 go ahead 18:16:08 I am ok with it being this time 18:16:10 .releng 9299 18:16:11 mboddu: Issue #9299: Large number of side tags is causing newRepo slowdowns - releng - Pagure.io - https://pagure.io/releng/issue/9299 18:16:34 But I guess its either cverna[m] or pingout to have a look at it 18:16:50 Is there a way to check if the side tags have been merged or not? 18:17:01 So, that we can remove the buildroots of them at least? 18:17:37 once they are merged they are delete. 18:17:39 deleted 18:17:40 * mboddu is having hard time with English today, will change to my native language :D 18:17:47 so the ones that exist are the ones that aren't merged yet 18:17:59 I dont think so, there is no clean up of this stuff 18:18:18 there's nothing to clean up old ones, but once merged they are deleted. 18:18:32 I opened a koji ticket on that... 18:18:52 https://pagure.io/koji/issue/2066 18:18:58 IIRC, cverna[m] said there is no clean up currently, but I am happy to be wrong in this case 18:19:03 but not sure what we can do to make them faster in the end. ;( 18:20:04 I guess, we have to ping ignatenkobrain since he has 146 side tags 18:20:40 he nuked most of them 18:21:04 ➜ ~ koji list-targets | grep side| wc -l 18:21:04 27 18:21:38 we could also @ mention the side tag author in that koji ticket... would have to find the plugin project again tho 18:22:25 ^ didn't get it 18:23:16 need to go deal with food in oven. 18:23:31 anything else for this meeting? 18:23:43 https://pagure.io/koji/issue/2066#comment-631788 18:24:04 mboddu: ^ asking the orig author to see if we missed something in setting it up or merging it into koji. 18:24:06 smooge: I guess this time seems to work, so thats all I guess 18:24:22 I thought I had something else, but now I can't recall. 18:24:35 nirik: Ah okay 18:26:00 ok, lets end then for today 18:26:03 #endmeeting