16:00:16 #startmeeting Fedora IoT Working Group Meeting 16:00:16 Meeting started Wed Feb 9 16:00:16 2022 UTC. 16:00:16 This meeting is logged and archived in a public location. 16:00:16 The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:16 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:16 The meeting name has been set to 'fedora_iot_working_group_meeting' 16:00:16 #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule 16:00:16 Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson 16:00:16 #topic roll call 16:00:27 * pwhalen is here 16:00:33 Good morning coremodule 16:00:37 hi pwhalen, good morning 16:00:49 We have IoT! 16:00:52 Yay! 16:01:12 heh, we do 16:01:40 openqa doesnt look good, but thats a needle issue by the looks of it 16:02:06 * pbrobinson is here 16:02:14 Okay, that's what I thought too, but I'll probably have to PM you to find out how to adjust needles... 16:02:32 Hi pbrobinson 16:03:14 hey 16:03:32 Lets get started 16:03:32 #topic 1) ==== Working Group process and admin  ==== 16:03:33 #link https://docs.fedoraproject.org/en-US/iot/ 16:03:50 Anything for docs? 16:04:12 I would like to write up a short doc on the IoT release cycle and wonder if there's a good time I can pick pbrobinson's brain for 15 minutes or so...? 16:04:16 #info pwhalen is moving over to a new role, he'll be leading more of the engineering side of Fedora IoT 16:04:34 Congratulations pwhalen! 16:04:36 sure, never a good time 16:04:45 what TZ are you on? 16:05:00 we basically aim to do monthly releases depending on other issues 16:05:26 pbrobinson, I'm MST, so UTC -7 16:05:28 it's mostly a rolling release in that we actively rebase the stable train to new releases on GA 16:06:14 it's not hugely complex because it doesn't need to be 16:06:28 I remember there was talk of two-week releases? has that changed, or is that just inaccurate? 16:08:06 no, I think that's FCOS 16:08:56 ah, okay. I got them confused. Okay, I'll ping you in #fedora-iot after the meeting and get some more details, just enough to write up a doc letting people know how and when to expect the next IoT 16:10:11 anything else for admin? 16:10:47 * pwhalen has nothing 16:11:05 #action coremodule to write doc detailing IoT release cycle 16:11:11 #topic 2) ==== Fedora 35 status ==== 16:11:11 #info Fedora-IoT-35-20220112.0 16:11:11 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20220112.0&groupid=1&groupid=5 16:11:32 #info Bug 2019579 - dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf' 16:11:46 #link https://bugzilla.redhat.com/show_bug.cgi?id=2019579 16:13:19 we've been blocked on this, we should have a compose later today, or tomorrow iiuc 16:13:48 That's good! 16:13:49 yes, I think that looks right, depends if we need anaconda stable in the main repo 16:14:13 either way once complete and tested we'll push this to be the latest stable release 16:15:23 #info New F35 IoT release incoming 16:16:53 How much longer will F35 IoT be around? Does it go away the day F36 GA is released? 16:17:12 yes 16:17:15 got it 16:17:49 And is that the day mainline F36 GA is released, or when F36 IoT is released? since the two aren't synced up in that regard 16:19:06 to date it's been GA date 16:19:17 I'm surprised you don't know most of this already coremodule 16:20:47 I'm just making sure that my info is accurate so the doc I write is accurate 16:21:27 alright, moving on to F36... 16:21:29 #topic 3) ==== Fedora 36 status ==== 16:21:29 #info Fedora-IoT-36-20220209.0 16:21:29 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220209.0&groupid=1&groupid=5 16:21:47 we have branched 16:21:54 Yay! 16:21:59 there is a compose, there will be another one shortly 16:22:04 yep, had to rebase to upgrade 16:22:26 yes, it's on devel branch as per our usual branched docs 16:23:35 We have an issue with wired network on the rpi4, but thats not officially supported. 16:24:21 coremodule: may I suggest the content of your docs ends up in our docs, I think these things are mostly in there, and if they're not they should be then they don't get lost in a random doc somewhere 16:24:22 openqa is failing due to issues with the needles, looks like they need to be updated 16:24:23 https://docs.fedoraproject.org/en-US/iot/ 16:24:48 pwhalen: I saw some fix that adam did on workstation needles but I think that was GUI 16:25:22 pbrobinson, yes, that is my plan 16:25:33 yea, looks like similar fixes are needed, its the graphical install 16:26:00 pwhalen: so maybe that will settle down in a day or so 16:26:39 RIght, I plan on doing manual testing today, filing some bugs on the kernel issues 16:29:20 alright, moving on to open floor 16:29:21 I would wait until the next compose completes, I'll do one once the tpm2 fix lands 16:30:07 ok, true. I'll look at our kernel issues first 16:31:00 #topic 4) ==== Open Floor ==== 16:31:06 anything for open floor? 16:33:01 rawhide compose won't be until tomorrow I suspect, we'll need to await a new one for mainline there 16:33:01 coremodule: probably need to add a rawhide/f37 item from next week too 16:33:01 #info pbrobinson suspects rawhide compose sometime tomorrow 16:33:01 pbrobinson, wiloc 16:33:01 *wilco 16:33:01 #info f37/rawhide will drop support for armhfp 16:33:47 we'll have parsec 1.0 at some point too, will give a heads up when that will land next week 16:34:37 Ok, sounds good. 16:36:36 thanks for the work getting to branched 16:36:45 ending meeting in 5... 16:36:51 4... 16:36:52 3... 16:36:54 2... 16:36:55 1... 16:37:00 #endmeeting