18:01:18 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:01:18 Meeting started Thu Jul 1 18:01:18 2021 UTC. 18:01:18 This meeting is logged and archived in a public location. 18:01:18 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:18 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:18 #chair mboddu nirik pingou mobrien nb 18:01:18 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:01:18 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:01:18 #info agenda is at https://board.net/p/fedora-infra-daily 18:01:18 Current chairs: mboddu mobrien nb nirik pingou 18:01:18 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:19 #info reminder: speak up if you want to work on a ticket! 18:01:21 #topic Tickets needing review 18:01:23 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:01:32 Sorta here 18:01:44 Well, in middle of something, but I can update the tickets 18:02:16 .ticket 10064 18:02:17 nirik: Issue #10064: bodhi commands fail: Token required but invalid - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10064 18:02:23 just needs 'waiting on asignee' 18:02:41 +1 18:02:48 .ticket 10065 18:02:52 nirik: Issue #10065: Add httpd keytab for Copr (production and dev instances) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10065 18:03:01 low low ops. I have some thoughts on this, but will add them later. 18:03:42 +1 18:03:46 (basically, I think we would really prefer moving to OIDC, not kerberos) 18:03:56 .ticket 10066 18:03:57 nirik: Issue #10066: src.fedoraproject.org displays wrong version - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10066 18:04:20 I'm not sure where it gets this info now. I think it used to be mdapi, but now might be packager dashboard? 18:04:36 low low ops, and @pingou to ask where it gets the info 18:04:54 and thats all the infra ones. 18:05:05 +1 18:06:01 No new releng one's but there is something I wanna discuss 18:06:59 #topic upcoming plans. 18:07:06 #monday is a holiday in the US 18:07:12 #info monday is a holiday in the US 18:07:29 #info monday and tuesday are holidays in CZ 18:07:43 #topic Discussion and AOB 18:07:47 go ahead. :) 18:08:33 nirik: https://pagure.io/releng/issue/10191#comment-741497, so I am going to create symlink SRPMS/ pointing to source/tree/ 18:08:47 But iirc, MM is not good with symlinks? 18:08:56 no no no 18:09:32 I can answer there 18:09:41 but we don't use symlinks because some mirrors cannot use them 18:09:52 we could hard link it for a short while and delete it later? 18:10:27 But that will add more data on the mirrors 18:11:20 not if hardlinked. 18:11:33 but I guess I don't get why they don't just fix their local config? 18:12:27 I guess they say it will take a while. 18:13:48 * mboddu is not thinking straight today 18:14:21 the hardlinking will be a pain tho. 18:14:39 basically we need to adjust new-updates-sync _again_ to sync to both 18:14:50 with hardlinking 18:14:54 Right 18:15:13 I wish asking them to update the config is the best way to go 18:15:17 or I suppose we could make some addon script that does the SRPM ones seperate 18:16:19 I suppose we could also do the symlinks and see who complains about their sync breaking... does quick-mirror-fedora handle symlinks? not sure. 18:17:19 Not that I know off, but even if we create the symlink what if the mirror they are using cant handle it 18:18:37 I don't know, depends on if it barfs on syncing it or if it just ignores it or what 18:18:55 Here's the plan, 1. Ask them to update their config. If they say it will take time, 2. Create hardlink for the time being and eventually remove it 18:19:35 We can explain them the 2nd option will take time from our end as well, it needs updates to scripts 18:19:40 they do say that already tho: 18:19:50 " 18:19:50 No, we are not, we point to our own mirror directly (https://linuxsoft.cern.ch/epel/). A symlink would be a backwards-compatible way of making this transition while we roll out new configuration files everywhere. (which will take quite a bit of time, given old docker and cloud images will continue to have the old repos...) 18:19:50 " 18:20:12 I asked them why they use the SRPM repos... 18:20:36 so yeah, fun. :( 18:21:15 Yup 18:22:42 Anyway, thats all I got 18:22:56 ok, then I will go back to it. :) 18:22:58 #endmeeting