<@abompard:matrix.org>
19:02:28
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@meetbot:fedora.im>
19:02:32
Meeting started at 2026-07-27 19:02:28 UTC
<@meetbot:fedora.im>
19:02:32
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@nirik:matrix.scrye.com>
19:02:39
!next
<@abompard:matrix.org>
19:02:39
!info Agenda is at https://board.net/p/fedora-infra-daily
<@abompard:matrix.org>
19:02:39
<@abompard:matrix.org>
19:02:39
!info Reminder: Speak up if you want to work on a ticket!
<@abompard:matrix.org>
19:02:39
<@abompard:matrix.org>
19:02:39
<@abompard:matrix.org>
19:02:39
!info Meeting is 30 minutes MAX. At the end of 30, its stops
<@abompard:matrix.org>
19:02:39
<@abompard:matrix.org>
19:02:39
!info invitees @smilner:fedora.im
<@abompard:matrix.org>
19:02:39
!chair @nirik:matrix.scrye.com, @phsmoura:fedora.im, @james:fedora.im
<@abompard:matrix.org>
19:02:39
<@abompard:matrix.org>
19:02:39
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@meetbot:fedora.im>
19:02:40
The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
<@nirik:matrix.scrye.com>
19:02:50
!next
<@abompard:matrix.org>
19:02:51
Run `!ticket #<number>` for each ticket, discuss and classify. DON'T DO THIS FOR PRIVATE TICKETS.
<@abompard:matrix.org>
19:02:51
<@abompard:matrix.org>
19:02:51
!info https://forge.fedoraproject.org/infra/tickets/issues?q=&type=all&sort=relevance&state=open&labels=0&milestone=0&project=0&assignee=0&poster=0
<@abompard:matrix.org>
19:02:51
!topic Tickets needing review
<@abompard:matrix.org>
19:02:51
<@nirik:matrix.scrye.com>
19:03:06
no new tickets.
<@nirik:matrix.scrye.com>
19:03:06
!next
<@abompard:matrix.org>
19:03:07
!topic Planning, Upcoming work and Open floor
<@nirik:matrix.scrye.com>
19:04:09
I'm gonna try and do some more rhel10 moves this week, but they all are tricky one way or another. ;) I am considering a outage (possibly thursday?) to do all the vmhost/bvmhosts that are left (the ones with outage causing things on them). Also considering starting on database servers.
<@nirik:matrix.scrye.com>
19:05:15
I'm also doing openshift cluster updates because we got a bit behind.
<@james:fedora.im>
19:08:11
Gah, sorry
<@james:fedora.im>
19:09:02
I'm looking at how to best get systemd creds things onto a machine via. ansible ... also looking at a maybe final attempt at getting koji.stg to work.
<@james:fedora.im>
19:09:37
I tried a few things, and they all imply the ansible task should work fine ... that the backup is fine, etc.
<@nirik:matrix.scrye.com>
19:10:22
so on creds... IMHO it's fine to just have them be manual to start with and we can sort out automating that later... if that helps any move the rest forward?
<@nirik:matrix.scrye.com>
19:10:52
yeah, that error is quite odd. Let me know if you want me to stare at it anymore.
<@james:fedora.im>
19:12:49
I'm running the playbook again atm. (been running a couple of hours already) and I've looked at it a bunch ... but if it doesn't work somehow very soon ¯\\\_(ツ)\_/¯
<@nirik:matrix.scrye.com>
19:13:57
yeah, if it croaks again, save off the full error and I can look at it and scratch my head some.
<@james:fedora.im>
19:13:58
I also downloaded a backup to disk, and it looked fine to me ... but checking 750GB+ sql taxes lots of things.
<@nirik:matrix.scrye.com>
19:14:11
yep. It's a monster.
<@nirik:matrix.scrye.com>
19:15:39
anything else to bring up today?
<@james:fedora.im>
19:16:13
Not here.
<@nirik:matrix.scrye.com>
19:17:14
alrightly, back at it then...
<@nirik:matrix.scrye.com>
19:17:17
!endmeeting