<@angelcr:matrix.org>
15:29:44
!startmeeting fedora_coreos_meeting
<@meetbot:fedora.im>
15:29:46
Meeting started at 2026-08-12 15:29:44 UTC
<@meetbot:fedora.im>
15:29:46
The Meeting name is 'fedora_coreos_meeting'
<@angelcr:matrix.org>
15:29:57
!topic roll call
<@hricky:fedora.im>
15:31:12
!hi
<@zodbot:fedora.im>
15:31:13
Hristo Marinov: Hristo Marinov (hricky) - he / him / his
<@spresti:fedora.im>
15:32:14
!hi
<@angelcr:matrix.org>
15:32:59
!topic Action items from last meeting
<@marmijo:fedora.im>
15:33:06
!hi
<@zodbot:fedora.im>
15:33:09
marmijo: Michael Armijo (marmijo)
<@spresti:fedora.im>
15:33:15
!hi
<@cadejacobson:matrix.org>
15:33:15
!hi
<@zodbot:fedora.im>
15:33:17
spresti: Steven Presti (spresti)
<@zodbot:fedora.im>
15:33:18
Cade: Cade Jacobson (cadejacobson)
<@angelcr:matrix.org>
15:33:26
!info there are no action items from the last meeting.
<@angelcr:matrix.org>
15:33:44
!topic Review Fedora 45 Release Schedule
<@angelcr:matrix.org>
15:33:52
<@marmijo:fedora.im>
15:35:13
Fedora 45 branched from rawhide yesterday!
<@ydesouza:fedora.im>
15:35:14
!hi
<@angelcr:matrix.org>
15:35:19
It seems that yesterday there were to key dates:
<@angelcr:matrix.org>
15:35:19
1. Change Checkpoint: Completion deadline (testable)
<@angelcr:matrix.org>
15:35:19
2. Branch Fedora Linux 45 from Rawhide
<@angelcr:matrix.org>
15:35:19
<@angelcr:matrix.org>
15:35:19
And we are currently in a Post-branch Freeze that will end the 14th
<@jcapitao:matrix.org>
15:35:30
!hi
<@zodbot:fedora.im>
15:35:32
jcapitao: Joel Capitao (jcapitao) - he / him / his
<@rapneset:matrix.org>
15:35:36
!hi
<@ravanelli:matrix.org>
15:36:17
!hi ravanelli
<@zodbot:fedora.im>
15:36:22
Renata Ravanelli: Renata Ravanelli (ravanelli)
<@marmijo:fedora.im>
15:36:40
I went ahead and opened some PRs to move branched to f45 and enable the stream, but we're still waiting on f45 bootc images for those to land
<@peytonrobertson:matrix.org>
15:37:20
!hi
<@zodbot:fedora.im>
15:37:24
No Fedora Accounts users have the @peytonrobertson:matrix.org Matrix Account defined
<@dustymabe:matrix.org>
15:37:39
marmijo: IIRC we always end up in a tizzy because `rawhide` starts breaking because things starting getting signed with a F46 key and `coreos-installer` needs to be updated with the new key.
<@dustymabe:matrix.org>
15:37:39
<@dustymabe:matrix.org>
15:37:39
though maybe we started fixing that in the last cycle so we wouldn't have this problem. Not sure, but worth checking
<@marmijo:fedora.im>
15:39:12
dustymabe: I'll keep an eye out for that. I have the F46 signing key changes to coreos-installer staged for a PR, but it'll require a release I think
<@angelcr:matrix.org>
15:39:41
!topic No meeting topics found.
<@angelcr:matrix.org>
15:40:14
We have no topics this week, so we can move onto the open floor
<@angelcr:matrix.org>
15:40:17
!topic Open Floor
<@dustymabe:matrix.org>
15:40:23
Sorry I was out last week. /me is reminded to go look at previous meeting notes.
<@rapneset:matrix.org>
15:42:19
Am I remembering correctly that we meant to ask Peyton Robertson something last week? Related to flatcar?
<@dustymabe:matrix.org>
15:43:31
yeah. basically wanted to run the butane merge by the flatcar team again: https://github.com/coreos/ignition/pull/2235
<@dustymabe:matrix.org>
15:43:49
congrats spresti on getting that PR in
<@spresti:fedora.im>
15:44:12
Thank you dustymabe miiid progress, updating docs and CI soon to fully archive butne
<@spresti:fedora.im>
15:44:17
Thank you dustymabe miiid progress, updating docs and CI soon to fully archive butane
<@peytonrobertson:matrix.org>
15:44:32
I haven't gotten any feedback from them directly about it, but let me reach out again and see if they have anything to say about it!
<@spresti:fedora.im>
15:44:46
Full context https://fedoraproject.org/wiki/Changes/IgnitionNativeButaneSupport
<@rapneset:matrix.org>
15:44:49
Thanks Peyton Robertson
<@rapneset:matrix.org>
15:45:45
For https://github.com/coreos/fedora-coreos-tracker/issues/2203, should we just promote testing/next since testing-devel has a patched kernel version?
<@dustymabe:matrix.org>
15:46:48
i.e. an out of band update?
<@rapneset:matrix.org>
15:47:07
Yeah I guess so. Or what would you suggest?
<@dustymabe:matrix.org>
15:48:06
i guess it depends on the severity. I'm not good at judging these things. usually rely on travier for that
<@dustymabe:matrix.org>
15:48:37
if we wanted to what I would suggest is just promoting the fixed kernel into `testing` and `next` and then doing an out of band build for them + ship ASAP
<@dustymabe:matrix.org>
15:48:48
then the `stable` update next week would get the fix too
<@angelcr:matrix.org>
15:49:18
> i guess it depends on the severity. I'm not good at judging these things. usually rely on travier for that
<@angelcr:matrix.org>
15:49:18
<@angelcr:matrix.org>
15:49:18
Did we do anything for januscape ? If the CVE is different maybe we can use that to judge what we should do now.
<@angelcr:matrix.org>
15:50:08
> i guess it depends on the severity. I'm not good at judging these things. usually rely on travier for that
<@angelcr:matrix.org>
15:50:08
<@angelcr:matrix.org>
15:50:08
Did we do anything for januscape ? If the CVE isnt too different maybe we can use that to judge what we should do now.
<@rapneset:matrix.org>
15:50:24
https://github.com/coreos/fedora-coreos-tracker/issues/2183
<@marmijo:fedora.im>
15:53:03
The tracker issue for januscape was created after the FCOS version that included the fix had already been built (but not yet released). So this situation is a little different, since we're in between releases.
<@marmijo:fedora.im>
15:55:48
If we promote testing/next now, we wont get much time for it to bake before hitting stable next week, though it'll be the only change since the previous release. How severe is this?
<@rapneset:matrix.org>
15:55:53
In terms of severity dustymabe, the below links give Januscape a 7.8 and Zapscape a 7:
<@rapneset:matrix.org>
15:55:53
<@rapneset:matrix.org>
15:55:53
https://access.redhat.com/security/cve/cve-2026-53359
<@rapneset:matrix.org>
15:55:53
https://access.redhat.com/security/cve/cve-2026-64561
<@dustymabe:matrix.org>
15:56:55
I'm happy with either option.
<@dustymabe:matrix.org>
15:57:46
This does require a specific type of workload (VMs) so it shouldn't affect our entire user base, but having a bad security issue isn't good either
<@angelcr:matrix.org>
15:58:21
It also needs to have root access inside the VM, it seems form the readme
<@dustymabe:matrix.org>
16:00:41
Angel Cervera Roldan: right, which may not be uncommon.. part of the reason to use a VM is because of the security boundary, so giving out root is acceptable so people can "do whatever they want"
<@rapneset:matrix.org>
16:02:46
Any objections to promoting next/testing then?
<@angelcr:matrix.org>
16:02:46
That makes sense. I like the idea of the promoting the kernel and shipping
<@dustymabe:matrix.org>
16:03:27
rapneset: i'm on board. but to be clear, we're not promoting testing-devel/next-devel - just fast-tracking the kernel update in existing testing/next
<@marmijo:fedora.im>
16:04:00
I'm +1 as well to an out-of-band update for it
<@rapneset:matrix.org>
16:04:10
Yes ok. How is that usually done?
<@dustymabe:matrix.org>
16:06:33
rapneset: should be able to run the "Add package override" github action in the repo
<@dustymabe:matrix.org>
16:06:39
https://github.com/coreos/fedora-coreos-config/actions
<@marmijo:fedora.im>
16:08:01
I created release trackers for testing/next, so once those PRs merge I don't mind performing the releases
<@marmijo:fedora.im>
16:08:17
I created release trackers for testing/next, so once those override PRs merge I don't mind performing the releases
<@zodbot:fedora.im>
16:08:38
acervera has already given cookies to marmijo during the F44 timeframe
<@rapneset:matrix.org>
16:09:53
For fast track, do I need to find the bodhi link or is the version enough
<@dustymabe:matrix.org>
16:11:57
rapneset: I find the bodhi link is easier.. grab it from one of https://bodhi.fedoraproject.org/updates/?search=&packages=kernel&releases=F44
<@rapneset:matrix.org>
16:12:39
Ok thanks
<@angelcr:matrix.org>
16:14:49
We have another 15m left, so if anyone else has a topic they would like to bring up, we have enough time
<@angelcr:matrix.org>
16:19:32
It seems like there are no more topic, so I will end the meeting a little bit earlier than scheduled. Thanks everyone for attending!
<@angelcr:matrix.org>
16:19:59
!endmeeting