2025-10-09 19:03:24 <@nirik:matrix.scrye.com> !startmeeting Fedora Infrastructure Ops Daily Standup Meeting
2025-10-09 19:03:25 <@meetbot:fedora.im> Meeting started at 2025-10-09 19:03:24 UTC
2025-10-09 19:03:25 <@meetbot:fedora.im> The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
2025-10-09 19:03:30 <@james:fedora.im> Hey
2025-10-09 19:03:33 <@nirik:matrix.scrye.com> !info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
2025-10-09 19:03:33 <@nirik:matrix.scrye.com> !meetingname fedora_infrastructure_ops_daily_standup_meeting
2025-10-09 19:03:33 <@nirik:matrix.scrye.com> !info meeting is 30 minutes MAX. At the end of 30, its stops
2025-10-09 19:03:33 <@nirik:matrix.scrye.com> !info agenda is at https://board.net/p/fedora-infra-daily
2025-10-09 19:03:33 <@nirik:matrix.scrye.com> !info reminder: speak up if you want to work on a ticket!
2025-10-09 19:03:33 <@nirik:matrix.scrye.com> !topic Tickets needing review
2025-10-09 19:03:34 <@meetbot:fedora.im> The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
2025-10-09 19:03:47 <@nirik:matrix.scrye.com> morning
2025-10-09 19:03:56 <@nirik:matrix.scrye.com> !ticket 12837
2025-10-09 19:03:57 <@zodbot:fedora.im> ● **Last Updated:** Never
2025-10-09 19:03:57 <@zodbot:fedora.im> 
2025-10-09 19:03:57 <@zodbot:fedora.im> **fedora-infrastructure #12837** (https://pagure.io/fedora-infrastructure/issue/12837):**Opt-in for AWS region to ap-southeast-6 acct:125523088429**
2025-10-09 19:03:57 <@zodbot:fedora.im> ● **Assignee:** Not Assigned
2025-10-09 19:03:57 <@zodbot:fedora.im> ● **Opened:** 53 minutes ago by mnguyen
2025-10-09 19:04:04 <@nirik:matrix.scrye.com> low low? assign to me?
2025-10-09 19:04:21 <@james:fedora.im> Sure
2025-10-09 19:04:53 <@nirik:matrix.scrye.com> !topic work plans / upcoming tasks
2025-10-09 19:05:16 <@nirik:matrix.scrye.com> The connection timeout thing is still not solved, but the retries seem to be papering over it nicely so far.
2025-10-09 19:06:52 <@nirik:matrix.scrye.com> otherwise I have stuff mentioned in my standupbot post.
2025-10-09 19:07:42 <@nirik:matrix.scrye.com> The rdu2-cc -> rdu3 datacenter move has moved out some... likely early december now (or if not, will slip out to next year)
2025-10-09 19:08:45 <@james:fedora.im> Yeh, I also spoke to the bot ... hopefully fix the proxy disk space thing before next Tuesday. Maybe refresh some certificates so we get to keep SSL running ;)
2025-10-09 19:09:59 <@nirik:matrix.scrye.com> those openshift api certs are a bit different, but I can go over how to renew them (They are currently letsencrypt I think, but we could move them to digicert I guess)
2025-10-09 19:10:58 <@james:fedora.im> I'm fine leaving OpenShift to someone else ... also thought you could do some kind of auto renew with letsencrypt.
2025-10-09 19:11:33 <@nirik:matrix.scrye.com> well, they involve getting the cert (which needs a dns challenge) and then loading them into openshift (needing some oc commands).
2025-10-09 19:11:55 <@nirik:matrix.scrye.com> ¯\\\_(ツ)\_/¯ It could be automated, but...
2025-10-09 19:12:18 <@nirik:matrix.scrye.com> anyhow... I don't think I have anything more... unless there's something someone would like to discuss?
2025-10-09 19:14:20 <@james:fedora.im> I'm good.
2025-10-09 19:14:33 <@nirik:matrix.scrye.com> ok, thanks...
2025-10-09 19:14:38 <@nirik:matrix.scrye.com> !endmeeting