15:01:10 <coremodule> #startmeeting Fedora IoT Working Group Meeting
15:01:10 <zodbot> Meeting started Wed Oct  5 15:01:10 2022 UTC.
15:01:10 <zodbot> This meeting is logged and archived in a public location.
15:01:10 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:01:10 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:10 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
15:01:10 <coremodule> #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule
15:01:10 <coremodule> #topic roll call
15:01:11 <zodbot> Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson
15:01:24 * pwhalen is here
15:01:29 <coremodule> hi pwhalen
15:02:13 <pwhalen> Howdy coremodule, how goes?
15:02:29 <coremodule> so far, so good! how are you?
15:02:55 <pwhalen> Not too bad, fighting off the beginnings of a cold I think.
15:03:13 <coremodule> oooh yuck. It's that time of year now I guess... not a fan
15:03:35 * miabbott wonders who isn't sick among us :P
15:03:48 <pwhalen> howdy miabbott! Welcome
15:03:54 <miabbott> o/
15:04:08 <coremodule> hi miabbott
15:04:11 <coremodule> let's get started
15:04:13 <coremodule> #topic 1) ==== Working Group process and admin  ====
15:04:13 <coremodule> #link https://docs.fedoraproject.org/en-US/iot/
15:05:01 <pwhalen> I dont have anything for docs this week, but likely will in weeks to come
15:05:06 <coremodule> I don't have anything for docs/admin, anyone else?
15:05:09 <coremodule> okay, sounds good
15:06:15 <coremodule> #topic 2) ==== Fedora 36 status ====
15:06:15 <coremodule> #info Fedora-IoT-36-20220718.0
15:06:15 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220718.0&groupid=1&groupid=5
15:06:38 <coremodule> Anything for F36 today? I haven't looked in a month. Doesn't look like any changes.
15:07:01 * pwhalen tries to remember why its failing
15:07:22 <coremodule> systemd issue I think...
15:07:34 <coremodule> wait
15:07:36 <pwhalen> armhfp?
15:08:24 <pwhalen> ah right, disk image fails, I think because of the date
15:08:37 <pwhalen> https://koji.fedoraproject.org/koji/taskinfo?taskID=92566500
15:10:28 <pwhalen> f37 is around the corner too, and f36 is getting updates.. so
15:10:41 <coremodule> #info F36 IoT composes failing because of an issue with the date
15:10:55 <coremodule> that's been my attitude too...
15:11:19 <coremodule> we'll just... move on, for now
15:11:22 <coremodule> #topic 3) ==== Fedora 37 status ====
15:11:22 <coremodule> #info Fedora-IoT-37-20221005.0
15:11:22 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20221005.0&groupid=1&groupid=5
15:11:24 <pwhalen> specifically armhfp, I think the containers have been failing for the same reason in mainline
15:11:41 <pwhalen> thankfully this looks better, no armhfp
15:11:51 <coremodule> yes! this is good!
15:12:44 <pwhalen> on parsec, I mentioned I reproduced what you saw on the rpi400 on my RPi3
15:12:51 <coremodule> #info F37 is looking good in openQA.
15:13:03 <pwhalen> RPi4-4gb was fine, as was the fitlet2
15:13:29 <coremodule> ah yeah, I saw that. Interesting, I used an rpi400 4gb to do my testing and got that failure each time...
15:13:33 <pwhalen> I redeployed my RPi3 with a newer compose, and it worked ok. Redeployed the other two and they were fine as well
15:13:34 <coremodule> I can try on rpi3 and see what happens
15:13:57 <pwhalen> so, maybe try a newer compose on the RPi400, see if it helps.
15:13:58 <coremodule> good to know. my image that i used to test on was an older compose that had been updated to the latest, perhaps there was an issue there
15:14:13 <coremodule> alright, I will do that after the meeting
15:14:57 <pwhalen> there is a newer parsec - https://bodhi.fedoraproject.org/updates/FEDORA-2022-d3f24658d2
15:15:10 <pwhalen> if you could add karma, that would be swell (provided this time it works :))
15:15:34 <coremodule> wilco. I'll test right after
15:15:53 <coremodule> #topic 4) ==== Fedora 38 status ====
15:15:53 <coremodule> #info Fedora-IoT-38-20221005.0
15:15:53 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=38&build=Fedora-IoT-38-20221005.0&groupid=1&groupid=5
15:16:03 <pwhalen> otherwise, things looked good.
15:17:20 <coremodule> F38 is looking ok
15:17:24 <coremodule> a few issues
15:17:33 <coremodule> and the x86_64 tests haven't finished
15:18:40 <pwhalen> nice. We're testing osbuild there, the raw disk images have been moved, the installer is now ready so I'll move that over likely today after some testing
15:20:16 <coremodule> cool, that's great. any issues you've encountered?
15:20:28 <pwhalen> so if you see breakage in rawhide, dont worry too much
15:20:46 <pwhalen> yes, there are a few issues. The partitioning wasnt quite right, included a bio boot partition
15:22:40 <coremodule> got it. okay, i'll inquire at next meeting how it's going
15:22:52 <pwhalen> I think thats about it for rawhide, but dont be surprised if it completely blows up
15:23:00 <coremodule> roger
15:23:06 <coremodule> #topic 5) ==== Open Floor ====
15:23:30 * pwhalen has nothing for open floor
15:23:53 <coremodule> I don't have anything here, there are 8 accepted blockers and 6 proposed currently, so we'll see what happens in the coming weeks
15:24:53 <pwhalen> new uboot, if you have cycles to test I think I saw pbrobinson proposed it as a FE for final
15:25:07 <coremodule> yes, I see it here. Okay, I can take a look
15:25:38 <pwhalen> thanks
15:25:46 <coremodule> alright, thanks for coming today
15:25:49 <coremodule> #endmeeting