16:01:34 <pwhalen> #startmeeting Fedora IoT Working Group Meeting
16:01:34 <pwhalen> #chair pwhalen pbrobinson coremodule
16:01:34 <pwhalen> #topic roll call
16:01:34 <zodbot> Meeting started Wed Mar  1 16:01:34 2023 UTC.
16:01:34 <zodbot> This meeting is logged and archived in a public location.
16:01:34 <zodbot> The chair is pwhalen. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:01:34 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:01:34 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
16:01:34 <zodbot> Current chairs: coremodule pbrobinson pwhalen
16:01:45 <pwhalen> Good morning, who's here today?
16:01:46 * coremodule is here.
16:01:54 * idiez is here
16:01:56 <sarmahaj> sarmahaj here
16:02:03 * djachimo is here
16:02:23 * copperi[m] is here
16:03:01 <pwhalen> Lots of people, welcome everyone. Just waiting for others to join
16:04:42 <pwhalen> #topic 1) ==== Working Group ====
16:05:08 <pwhalen> Does anyone have anything for admin this week?
16:05:25 * idiez has nothing
16:06:02 <pwhalen> I dont have anythign either.
16:06:23 <pwhalen> #topic 2) ==== Fedora 37 - Stable ====
16:06:27 * miabbott is here
16:06:39 <pwhalen> #link OpenQa Testing - https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20230228.0&groupid=1&groupid=5
16:07:04 <pwhalen> coremodule: did you have a chance to look at the rebase issue?
16:07:16 * pwhalen cant recall
16:08:09 <coremodule> I looked a while ago and thought it was fixed, but apparently not. I've been spread thin the last week with the all hands meeting, I will get to it
16:08:11 <pwhalen> otherwise, the rest are expected failures. For others - The clevis test on aarch64 has always failed, it should work now but I think the test needs to be adjusted.
16:09:10 <pwhalen> Zezere server has a bug on F37, I've not had a chance to look at it.
16:09:19 <pwhalen> coremodule: thanks
16:10:13 <pwhalen> I dont have anything else for F37.
16:10:34 <pwhalen> Anyone else?
16:10:50 <pwhalen> #topic 3) ==== Fedora 38 ====
16:10:50 <pwhalen> https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=38&build=Fedora-IoT-38-20230228.0&groupid=1&groupid=5
16:11:09 * pbrobinson is lurking, sorry I'm late
16:11:43 <pwhalen> And the same issues in Fedora 38.
16:13:21 <pwhalen> #info Fedora 38 Beta release targeted for Tue 2023-03-14
16:13:51 <pwhalen> We definitely have issues to solve before next week and RC's
16:14:08 <pwhalen> #info Build Fedora IoT Artifacts with osbuild
16:14:08 <pwhalen> #link https://fedoraproject.org/wiki/Changes/IoTArtifactsWithOSBuild
16:15:22 <pwhalen> This change has a number of issues to fix before an RC, currently the disk images do not boot on a raspberry pi
16:15:44 <miabbott> where are the issues tracked?
16:15:57 <pbrobinson> in the osbuild git hub
16:17:02 <pwhalen> We need a change to the partitioning on the disk images, and the RPi fw moved to the right place.
16:17:25 <pwhalen> #info AArch64 iot-raw-image should use '0x06' for ESP partition type (Raspberry Pi compatability)
16:17:35 <miabbott> i see 5 issues opened by pwhalen; i assume those are the ones that need fixing?
16:17:36 <pwhalen> #link https://github.com/osbuild/osbuild-composer/issues/3220
16:17:53 <pwhalen> #info RPi firmware and Uboot missing from esp partition on aarch64 iot disk images
16:18:03 <pwhalen> #link https://github.com/osbuild/osbuild-composer/issues/3312
16:18:27 <pwhalen> Those will 'fix' the disk images for the rpi.
16:18:53 <pwhalen> For the iso installer we have:
16:19:04 <pwhalen> #info iot-installer produced ISO fails to update "opening repo: opendir(/run/install/repo/ostree/repo): No such file or directory"
16:19:12 <pwhalen> #link https://github.com/osbuild/osbuild-composer/issues/3218
16:20:14 <pwhalen> #info iot-installer defaults to btrfs in Fedora 38
16:20:27 <pwhalen> #link https://github.com/osbuild/osbuild-composer/issues/3310
16:21:08 <pwhalen> Those are the issues I've found.
16:21:54 <miabbott> thanks pwhalen
16:21:56 <miabbott> do we expect that the osbuild folks will handle those?  or should the rhel for edge/fedora iot team be helping with all of them?
16:21:57 <pwhalen> Has anyone else done testing, seen anything I misseD?
16:22:47 <pwhalen> miabbott: I think we should likely look at them too
16:23:16 <pwhalen> Some of them are already being looked at, I think the fix for the partitioning is a pending PR
16:23:35 <miabbott> understood; i'll probably create some jira cards for our team for the unassigned ones.
16:24:15 <pwhalen> Ok, thanks.
16:24:36 <pwhalen> And for the simplified-installer we also have PR's pending
16:24:43 <idiez> I can look into the partitioning issue since I did the LVM partitioning for rhel
16:24:59 <miabbott> pwhalen++
16:24:59 <zodbot> miabbott: Karma for pwhalen changed to 2 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:25:02 <miabbott> idiez++
16:25:02 <zodbot> miabbott: Karma for idiez changed to 3 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:25:35 <pwhalen> that about covers all the issues I am aware of with our changes.
16:26:20 <pwhalen> Anything else for F38?
16:26:47 <pwhalen> I'm going to skip rawhide as we have another issue there and no composes since branching.
16:27:36 <pwhalen> #topic 4) ==== Open Floor ====
16:27:47 <pwhalen> Anything else to discuss this week?
16:27:54 <miabbott> i wanted to propose something for the fedora-iot GitHub org
16:28:16 <miabbott> i think it would beneficial to have a "catch-all" issue tracker for Fedora IoT problems
16:28:49 <miabbott> it would allow users to file issues that they are having with Fedora IoT and allow the community to help narrow down the cause and redirect folks to specific components
16:29:08 <miabbott> it also would provide a historical record of past problems that we could reference in the future
16:29:21 <pwhalen> I'm all for it
16:29:22 <miabbott> this is a similar model to what fedora silverblue and fedora coreos are using
16:29:31 <miabbott> https://github.com/fedora-silverblue/issue-tracker
16:29:34 <pbrobinson> yes, I looked at that and we discussed it previously but I don't remember where it went, I think we agreed it was a good idea
16:29:35 <miabbott> https://github.com/coreos/fedora-coreos-tracker/
16:29:57 <miabbott> ah ok! great!  i guess i'll stop trying to convince everyone  :P
16:30:50 <pbrobinson> and we did have that in pagure/what ever the other thing was, but other than what's needed for compose we moved docs and everything else to github
16:31:07 * miabbott nods
16:31:24 <pbrobinson> so from mem we were all agreed it was the right thing but I forget what happened, I probably dropped a ball
16:31:48 <miabbott> pbrobinson: it looks like you and patrick have admin to create new repos under fedora-iot
16:32:02 <miabbott> is that something you want to stick on your todo?  or delegate to someone else?
16:32:20 <pbrobinson> I can work with pwhalen to get it done
16:32:27 <miabbott> cool!
16:32:28 <pwhalen> Sounds good
16:32:34 <miabbott> pbrobinson++
16:32:34 <zodbot> miabbott: Karma for pbrobinson changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:32:45 <pwhalen> miabbott++
16:32:45 <zodbot> pwhalen: Karma for miabbott changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:33:04 <pwhalen> Anything else for this week?
16:33:21 <pwhalen> djachimo++
16:33:21 <zodbot> pwhalen: Karma for djachimo changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:33:25 <pwhalen> sarmahaj++
16:34:02 <pwhalen> hrm, maybe I gave out too many too quickly
16:34:42 <pwhalen> #endmeeting