#meeting-3:fedoraproject.org log

<@abompard:matrix.org>

19:01:19

!startmeeting Fedora Infrastructure Ops Daily Standup Meeting

<@meetbot:fedora.im>

19:01:21

Meeting started at 2026-03-26 19:01:19 UTC

<@meetbot:fedora.im>

19:01:21

The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'

<@smoliicek:fedora.im>

19:01:31

!next

<@phsmoura:fedora.im>

19:01:38

hello

<@smoliicek:fedora.im>

19:02:12

hello!

<@abompard:matrix.org>

19:02:36

!info invitees @smilner:fedora.im

<@abompard:matrix.org>

19:02:36

!chair @nirik:matrix.scrye.com, @phsmoura:fedora.im, @james:fedora.im

<@abompard:matrix.org>

19:02:36

<@abompard:matrix.org>

19:02:36

<@abompard:matrix.org>

19:02:36

!meetingname fedora_infrastructure_ops_daily_standup_meeting

<@abompard:matrix.org>

19:02:36

<@abompard:matrix.org>

19:02:36

!info Meeting is 30 minutes MAX. At the end of 30, its stops

<@abompard:matrix.org>

19:02:36

<@abompard:matrix.org>

19:02:36

!info Agenda is at https://board.net/p/fedora-infra-daily

<@abompard:matrix.org>

19:02:36

<@abompard:matrix.org>

19:02:36

!info Reminder: Speak up if you want to work on a ticket!

<@meetbot:fedora.im>

19:02:38

The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting

<@james:fedora.im>

19:03:01

Hey

<@smoliicek:fedora.im>

19:03:07

!next

<@james:fedora.im>

19:03:13

Nirik won't be around today ... so good times.

<@smoliicek:fedora.im>

19:03:37

yeah

<@abompard:matrix.org>

19:04:39

<@abompard:matrix.org>

19:04:39

Run `!ticket #<number>` for each ticket, discuss and classify. DON'T DO THIS FOR PRIVATE TICKETS.

<@abompard:matrix.org>

19:04:39

<@abompard:matrix.org>

19:04:39

!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:04:39

!topic Tickets needing review

<@smoliicek:fedora.im>

19:05:11

!link https://forge.fedoraproject.org/infra/tickets/issues/13226

<@james:fedora.im>

19:06:20

I guess it's low / 2 pts / day2day

<@smoliicek:fedora.im>

19:06:29

yeah, i agree

<@smoliicek:fedora.im>

19:07:20

!link https://forge.fedoraproject.org/infra/tickets/issues/13227

<@james:fedora.im>

19:08:13

med / 3 pts / day2day ?

<@james:fedora.im>

19:09:28

Need to ping someone who has done HW service stuff. But not sure who.

<@smoliicek:fedora.im>

19:09:35

<@smoliicek:fedora.im>

19:10:14

!link https://forge.fedoraproject.org/infra/tickets/issues/13229

<@james:fedora.im>

19:11:24

I think we just close this and point them at bugzilla?

<@james:fedora.im>

19:12:03

I guess against grub2, but not sure.

<@smoliicek:fedora.im>

19:13:12

just something like "Please report this as a bug on https://bugzilla.redhat.com/ against grub2"

<@james:fedora.im>

19:13:57

Yeh

<@james:fedora.im>

19:14:42

Maybe explain that "infra" is about problems related to the systems that packagers use to create fedora. And not usually for users of fedora.

<@smoliicek:fedora.im>

19:15:30

can you please send it, i need to take a call quickly

<@smoliicek:fedora.im>

19:15:31

sorry

<@james:fedora.im>

19:15:37

Sure, no problem

<@jcline:fedora.im>

19:18:01

Uh oh. We did just change how secure boot things get signed...

<@james:fedora.im>

19:20:31

In releng?

<@ahmedalmeleh:matrix.org>

19:20:32

So grub2 and secure boot are more user issues then?

<@james:fedora.im>

19:20:37

Is that likely to affect this?

<@jcline:fedora.im>

19:21:26

I'm trying to think. I've booted via that grub version right now so it's not generally broken. Either way it's better on a bugzilla against grub2.

<@james:fedora.im>

19:21:42

It's more "who can easily fix this" ... if releng changed something and it broke secure boot for newer grub2 packages, then it might need to be fixed by releng.

<@james:fedora.im>

19:21:57

But if grub2 just has a bug, then grub2 needs to fix it.

<@jcline:fedora.im>

19:21:59

Yeah, things are signed on the sigul server now, rather than via a smartcard on a special build host

<@jcline:fedora.im>

19:22:53

We flipped it over on Friday and https://bodhi.fedoraproject.org/updates/FEDORA-2026-632765fa87 went stable. Seems like a lot of people are noticing it's broken on the bodhi update

<@jcline:fedora.im>

19:23:33

Sorry, don't mean to derail your meeting, I'll go chat about this elsewhere

<@james:fedora.im>

19:23:49

Yeh, it seems good that you know about it at least.

<@james:fedora.im>

19:24:15

You should be able to comment on the infra issue for a bit, without reopening it

<@smoliicek:fedora.im>

19:24:18

sorry, i'm back

<@james:fedora.im>

19:24:43

n/p ... I think that was the last issue anyway.

<@smoliicek:fedora.im>

19:25:58

!next

<@abompard:matrix.org>

19:26:15

!topic Planning, Upcoming work and Open floor

<@smoliicek:fedora.im>

19:26:50

we have 5 minutes

<@james:fedora.im>

19:28:04

Yeh, did updates last night ... fixed a couple of things today with the updates+uptimes code, and everything looks good (apart from the machine that died on reboot ;).

<@james:fedora.im>

19:28:52

going to the dentist for an hour in a minute, so might not respond until later ;)

<@smoliicek:fedora.im>

19:29:05

i don't think i have anything

<@james:fedora.im>

19:29:17

Okay, thanks for running Vít Smolík

<@smoliicek:fedora.im>

19:29:23

!endmeeting