18:01:04 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:01:04 Meeting started Thu Oct 5 18:01:04 2023 UTC. 18:01:04 This meeting is logged and archived in a public location. 18:01:04 The chair is phsmoura. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:01:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:04 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:04 #chair nirik smooge phsmoura 18:01:04 Current chairs: nirik phsmoura smooge 18:01:04 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:01:04 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:04 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:01:04 #info agenda is at https://board.net/p/fedora-infra-daily 18:01:09 hello 18:01:53 morning, just finishing a fesco meeting 18:02:43 #info reminder: speak up if you want to work on a ticket! 18:02:43 #topic Tickets needing review 18:02:58 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:03:04 nothing new in infra 18:03:19 #info https://pagure.io/releng/issues?status=Open 18:03:34 .releng 11709 18:03:35 phsmoura: Issue #11709: Unretire rpms/python-APScheduler - releng - Pagure.io - https://pagure.io/releng/issue/11709 18:03:39 .releng 11710 18:03:39 phsmoura: Issue #11710: Unretire php-markdown - releng - Pagure.io - https://pagure.io/releng/issue/11710 18:03:46 both low low ops? 18:04:10 +1 18:05:46 #topic Planning, Upcoming work and Open floor 18:06:35 I'm still trying to get caught up this week. ;) Didn't get to docs or sigul stuff, but I still hope to later today/tomorrow. 18:08:21 Guessing you didn't get to the infra. ticket about log01, yet? 18:08:35 probibly not? which one? 18:08:44 oh, the one I haven't filed yet 18:08:49 Yeh 18:08:50 right. No, been in meetings. ;( 18:08:55 Yeh, no problem 18:09:12 Can wait until tomorrow, or whatever 18:09:19 let me do it now. ;) 18:09:19 Unless you want to talk about it now 18:10:45 so, this is last nights cron email: 18:10:48 https://paste.centos.org/view/77344d4b 18:11:33 Im having trouble to build a container and login in kerberos during the build. Im thinking maybe build the container without the pluto build script login in kerberos after deploying container and then run pluto build script and maybe add it in cron? 18:12:35 phsmoura: I think we have some other containers that use kerberos... might ask zlopez on it? I think he's set it up before (but I don't recall the details) 18:13:12 geppetto: so, I am not sure if the attempt 1 things are errors? or normal? but there's also some limits getting hit on the download servers and some other weird errors. 18:13:27 ah ok, Ill ping him. thanks :) 18:14:27 nirik: Yeh, I'd guess we want to allow our log file syncs. to ignore the limits for other people … if we can? 18:14:57 yeah, not sure if thats possible, but it might be. :) I'll file a ticket with the log to track it 18:15:14 * geppetto nods 18:15:49 Not sure what the proxy101.iad2.fedoraproject.org error means … there's no log file yet? 18:16:02 It'll get picked up tomorrow? 18:17:54 https://pagure.io/fedora-infrastructure/issue/11560 18:18:14 not sure, we can look at it. ;) 18:18:34 I can't login to that machine as me or root, which I assume is expected … feel free to ping me today or tomorrow if you want to look at it. 18:18:52 huh, I can get you access. ;) Just a sec. 18:19:17 well, but I guess it would be a freeze break. 18:19:41 so, yeah, I can gather info as needed if you let me know what to look for 18:19:53 * geppetto nods 18:21:29 anything else? 18:22:47 nothing from me off hand. 18:24:09 thanks nirik and geppetto 18:24:12 #endmeeting