<@abompard:matrix.org>
19:02:01
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@abompard:matrix.org>
19:02:01
!info Reminder: Speak up if you want to work on a ticket!
<@abompard:matrix.org>
19:02:01
<@abompard:matrix.org>
19:02:01
!info Agenda is at https://board.net/p/fedora-infra-daily
<@abompard:matrix.org>
19:02:01
<@abompard:matrix.org>
19:02:01
!info Meeting is 30 minutes MAX. At the end of 30, its stops
<@abompard:matrix.org>
19:02:01
<@abompard:matrix.org>
19:02:01
!chair @nirik:matrix.scrye.com, @phsmoura:fedora.im, @james:fedora.im
<@abompard:matrix.org>
19:02:01
<@abompard:matrix.org>
19:02:01
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@abompard:matrix.org>
19:02:01
<@abompard:matrix.org>
19:02:01
!info invitees @smilner:fedora.im
<@meetbot:fedora.im>
19:02:02
Meeting started at 2026-07-23 19:02:01 UTC
<@meetbot:fedora.im>
19:02:02
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@meetbot:fedora.im>
19:02:03
The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
<@nirik:matrix.scrye.com>
19:02:08
time for infra daily meeting?
<@james:fedora.im>
19:02:08
Hey
<@james:fedora.im>
19:02:31
!next
<@abompard:matrix.org>
19:02:32
<@abompard:matrix.org>
19:02:32
Run `!ticket #<number>` for each ticket, discuss and classify. DON'T DO THIS FOR PRIVATE TICKETS.
<@abompard:matrix.org>
19:02:32
!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:32
!topic Tickets needing review
<@abompard:matrix.org>
19:02:32
<@james:fedora.im>
19:02:43
No new tickets
<@james:fedora.im>
19:02:47
!next
<@abompard:matrix.org>
19:02:49
!topic Planning, Upcoming work and Open floor
<@james:fedora.im>
19:03:34
Mostly meetings so far, hopefully do a bit of siguldry work later.
<@kevin:fedoraproject.org>
19:04:59
federation is lagging again badly. Wonder if there's something that happens around this time. ;(
<@nirik:matrix.scrye.com>
19:05:02
sigh... lag... and then it even crashed my client... :(
<@james:fedora.im>
19:05:53
Was wondering ... you said you are going to re-sync. some things to batcave01, so you are planning on bringing up the old batcave as batcave02?
<@nirik:matrix.scrye.com>
19:06:03
!info batcave is switched to rhel10, please report any issues you see.
<@nirik:matrix.scrye.com>
19:07:05
no
<@nirik:matrix.scrye.com>
19:07:05
everything should be synced that I could think of...
<@nirik:matrix.scrye.com>
19:07:06
we still do have the disk if we need something, but hopefully not...
<@nirik:matrix.scrye.com>
19:07:13
I did a re-sync before taking the old one down... so it was up to date.
<@nirik:matrix.scrye.com>
19:07:56
/home, /srv, /root, /var/log/ansible all should be synced and up to date. If there's something missing let me know
<@james:fedora.im>
19:08:07
Ahh, my bad, I must have misread what you said to someone
<@james:fedora.im>
19:08:36
FWIW it looks the same to me, so far.
<@nirik:matrix.scrye.com>
19:08:56
well, there were some db-dumps I didn't finish syncing, but they should be synced now (from their db servers)
<@nirik:matrix.scrye.com>
19:09:14
I'm sure we will hit some ansible fun with the version jump.
<@nirik:matrix.scrye.com>
19:09:27
I may do a check-diff run soon, or just a real run and see what blows up
<@james:fedora.im>
19:11:46
I see you already moved the facts cache for 01 ... is it fine to keep it for everything else?
<@nirik:matrix.scrye.com>
19:12:24
I think so. yeah, I had to regen the 01 one since it changed...
<@nirik:matrix.scrye.com>
19:14:55
I'm also thinking about a outage next week... to move some more things to rhel10, but it's only partly formed in my brain, so will ponder on exactly what to do more.
<@james:fedora.im>
19:15:44
Okay
<@nirik:matrix.scrye.com>
19:16:50
nothing more off hand from me.
<@james:fedora.im>
19:17:37
Okay.
<@james:fedora.im>
19:17:39
!endmeeting