16:30:21 #startmeeting fedora_coreos_meeting 16:30:21 Meeting started Wed Mar 15 16:30:21 2023 UTC. 16:30:21 This meeting is logged and archived in a public location. 16:30:21 The chair is ravanelli. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:30:21 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:30:21 The meeting name has been set to 'fedora_coreos_meeting' 16:31:07 .hello c4rt0 16:31:09 apiaseck: c4rt0 'Adam Piasecki' 16:31:15 .hello davdunc 16:31:16 davdunc[m: davdunc 'David Duncan' 16:31:21 #chair c4rt0 16:31:21 Current chairs: c4rt0 ravanelli 16:31:23 .hello2 16:31:24 jlebon: jlebon 'None' 16:31:31 .hi 16:31:32 dustymabe: dustymabe 'Dusty Mabe' 16:31:49 #chair davdunc jlebon dustymabe 16:31:49 Current chairs: c4rt0 davdunc dustymabe jlebon ravanelli 16:32:59 .hello spresti 16:33:00 spresti[m]: spresti 'Steven Presti' 16:33:19 #chair spresti 16:33:19 Current chairs: c4rt0 davdunc dustymabe jlebon ravanelli spresti 16:34:03 Ok, let's start 16:34:12 #topic roll call 16:34:38 #topic Action items from last meeting 16:34:53 #info there were no action items from last meeting 16:35:13 Should we go over Fedora 38 changes considerations? 16:35:18 woohoo! 16:35:36 ravanelli: +1 16:35:37 ravanelli: sounds good 16:35:46 #topic tracker: Fedora 38 changes considerations 16:35:54 #link https://github.com/coreos/fedora-coreos-tracker/issues/1357 16:36:19 i think we have just a few items left here 16:36:28 subtopic 127. z13 as the Baseline for IBM Z Hardware 16:36:29 Where did we stop in the list? 16:36:42 #link https://fedoraproject.org/wiki/Changes/z13BaselineForIBMZ 16:37:37 dustymabe: Do you have more info about it? 16:37:42 i think we can safely assume there's no immediate work necessary for this one 16:38:07 ravanelli: not much more than what's in the change proposal 16:38:20 jlebon: i'm wondering if we need to add any info to https://docs.fedoraproject.org/en-US/fedora-coreos/platforms/#_s390x for Z 16:38:32 or maybe we just leave it be 16:39:27 Can we ask someone internally to take a look on it? And see what it may take? 16:39:36 dustymabe: good point. maybe? apparently z13 is obsolete so i'd be surprised if it were available in the cloud. 16:39:53 #info nothing for us to do as this is just gcc and kernel compiler flags, which we'll pick up transparently. Hopefully our users aren't using anything older than z13. 16:40:14 ravanelli: I don't think there is any work for us to do because we just pick up the RPMs (already compiled) 16:40:22 but yeah, users theoretically could be running FCOS on z13 today 16:40:31 dustymabe: ok 16:40:37 z13 == OK 16:40:42 older than z13, not OK 16:40:44 :) 16:40:51 oh right, thanks 16:41:06 subtopic 128. Pcre Deprecation 16:41:15 #link https://fedoraproject.org/wiki/PcreDeprecation 16:41:15 and "zEC12" is what is obsolete 16:42:08 we already inherited this change with pcre dropping out in f38 16:42:37 it's a pure library, no binaries 16:42:39 this particular change says it's just deprecation, not retirement (which will come later) 16:43:13 retirement is: Targeted release: Fedora Linux 41 16:43:24 jlebon, but you say we already dropped out pcre? 16:43:47 https://github.com/coreos/fedora-coreos-tracker/issues/1435#issuecomment-1458847358 16:43:52 perfect! 16:44:03 it was nice to be able to link to that wasn't it :) 16:44:27 #info the pcre package was removed in f38 from FCOS; nothing further for us to do 16:44:43 i suppose, though PR comments can be linked too :) 16:44:49 subtopic 129. X Server Prohibits Byte-swapped Clients 16:45:04 #link https://fedoraproject.org/wiki/Changes/XServerProhibitsByteSwappedClients 16:45:34 skiiiiiiiiip 16:46:11 #info this shouldn't affect us, no X servers in FCOS 16:46:22 subtopic 130. Unified Kernel Support Phase 1 16:46:30 #link https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_1 16:47:24 no immediate action needed, but part of a larger discussion around confidential computing 16:47:42 #info no immediate action needed, but part of a larger discussion around confidential computing 16:48:06 interesting to read the plans for ppc64le and s390x there 16:48:09 optional RPMs and build tooling certainly would make it easier to play with 16:48:36 "s390x: no plans" 16:49:11 it's going to be even harder to keep track of the differences across arches 16:49:26 jlebon: isn't that kind of what secex for s390x is trying to achieve, though? 16:50:14 dustymabe: indeed. but in a totally different way. ideally, there's things we can unify on but i'm not sure how feasible that is. 16:50:43 +1 16:50:52 ok that's all the changes that were outstanding I think 16:51:50 +1 16:51:54 Is there anything else we should go through? 16:52:03 ravanelli: there is one more `meeting` ticket 16:52:56 dustymabe: which one? 16:53:11 https://github.com/coreos/fedora-coreos-tracker/labels/meeting 16:54:04 #topic Fedora 38 Test Week 16:54:15 #link https://github.com/coreos/fedora-coreos-tracker/issues/1440 16:54:59 this was opened by SumantroMukherje 16:55:16 I think last cycle jbrooks ran the test day for us (with help from miabbott) 16:55:57 we're ready for this too, because we have a `next` release that went out yesterday. 16:56:16 I can try to run it, with some help 16:56:27 that would be amazing ravanelli! 16:56:33 timeline-wise, are we thinking next week? 16:56:36 ravanelli++ 16:56:45 jlebon: let's look at the f38 schedule 16:57:01 https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html 16:57:12 final freeze starts on April 4th 16:57:38 so we could wait until say the 28th to run our test day if we wanted 16:58:03 .hi siosm 16:58:04 travier: Sorry, but user 'travier' does not exist 16:58:07 but next week would be better, though there is work to do to prepare for test day 16:58:09 .heloo siosm 16:58:11 .hello siosm 16:58:12 travier: siosm 'Timothรฉe Ravier' 16:58:24 #chair siosm 16:58:24 Current chairs: c4rt0 davdunc dustymabe jlebon ravanelli siosm spresti 16:58:29 dustymabe: +1 16:58:36 if changes are needed in pkgs, we need to give time to maintainers 16:58:45 so my proposal would be end of next week or early the following week 16:59:21 my vote is for next week 16:59:52 WFM, but we'll have to get on the checklist in the ticket soon 17:00:09 #proposed Start our Fedora 38 Test Week next week 17:00:28 dustymabe: end of next week, e.g. thursday or friday? 17:00:51 ravanelli: let's try to target a day (we can always allow users to submit results anytime during the week, but we want to try to coordinate a critical time when we'll be around) 17:01:16 jlebon: yeah, thursday or friday (though Friday's aren't great) 17:01:25 thursday so 17:01:32 +1 17:02:06 hmm, if things need to be ready by monday though (to allow users to go through tests and report results), then it's tight 17:02:40 it's usually a progression.. we don't have to make it a week 17:02:42 we can make it a day 17:02:56 i think we made it a week in the past to try to allow people more time and flexibility 17:03:07 Monday maybe in this case 17:03:11 but if our schedule is tight we can target a day 17:03:26 ok cool, that's better 17:03:51 maybe we can meet at some point this week just to go over what needs to get done 17:04:04 jlebon: +1 17:04:25 sounds good to me - tomorrow or friday morning? 17:04:48 dustymabe: I think we said we would go over beaker on Friday 17:05:06 oh yeah, the maintenance window thing we already scheduled 17:05:08 good point :) 17:05:35 tomorrow is 17:05:55 might be afk tmw, but definitely will be able to help with the things output from that meeting 17:06:50 ravanelli: we'll just leave it up to you :) - use your best judgement (the pre-meeting isn't really super important as long as it happens at some point) 17:07:41 #proposed We will meet tomorrow (03/16) to discuss the next steps about our Fedora 38 Test Week 17:08:05 I will some guidance for how to do it, maybe we can also go over it tomorrow 17:08:18 and.. tentatively the test day will happen on the 23rd (one week later) 17:08:22 +1 17:08:25 s/I will/ I will need 17:08:33 ravanelli++ 17:08:33 dustymabe: Karma for ravanelli changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:08:40 +1 17:09:44 #agreed We will meet tomorrow (03/16) to discuss the next steps about our Fedora 38 Test Week and tentatively the test day will happen on the 23rd (one week later) 17:09:59 ๐ŸŽ‰ 17:10:16 Should we go to Open Floor? 17:10:23 ๐Ÿ‘ 17:10:36 #topic Open Floor 17:11:10 so... I just hit what may be a (temporary) blocker for us rolling out the f38 update 17:11:26 i went to pre-upgrade my AWS blog node and it didn't come back 17:11:45 :( 17:11:49 grub complains - secondary boot entry works fine 17:11:57 :( 17:12:18 is this one of the known AWS issues? 17:12:20 in kernel 6.2 they changed the format of the kernel for aarch64 17:12:27 jlebon: not that I know of 17:12:42 my node was initially provisioned with `34.20210904.2.0` 17:12:56 i'm guessing that my bootloader is now too old to boot the new kernel/initrd 17:13:10 but this does present a problem for automatically updating systems 17:13:22 either way.. i've got some more investigation to do 17:13:35 ouch 17:13:58 but... I would expect us to block on this until we at least understand the problem more and give our users some guidance (i.e. maybe have them actually use bootupd) 17:14:31 * dustymabe wonders if adamw has seen anything like this 17:14:40 if you don't have console access to rollback, the node is basically lost, right? 17:14:46 that's an interesting case dustymabe 17:14:48 jlebon: correcto 17:15:04 * dustymabe plans to open an issue soon with more details and the actual error message 17:15:28 how do I always find the bugs!! ๐Ÿชฒ 17:15:29 ok yeah, let's do that. we also really need to beef up our upgrade testing story 17:15:33 ๐Ÿ› ๐Ÿž 17:15:48 jlebon: right. this might not be specific to AWS TBH 17:15:54 if i'm right, it probably isn't 17:16:00 right 17:16:14 * jlebon tries to find the issue he filed related to this 17:16:39 that's all I had for open floor (sorry to dampen the mood) 17:16:43 anyone with anything else? 17:17:27 https://github.com/coreos/coreos-assembler/issues/2519 17:18:20 and we really should figure out what's left to do to get bootupd enabled by default 17:19:06 +1 17:20:46 dustymabe: thanks for doing the f38 rebase release! 17:21:12 jlebon: np :) 17:21:30 ravanelli: if there's nothing else, I think we can close this meeting :) 17:21:36 #endmeeting