16:01:55 <coremodule> #startmeeting Fedora IoT Working Group Meeting
16:01:55 <zodbot> Meeting started Wed Feb 16 16:01:55 2022 UTC.
16:01:55 <zodbot> This meeting is logged and archived in a public location.
16:01:55 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:01:55 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:01:55 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
16:01:57 <coremodule> #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule
16:01:57 <zodbot> Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson
16:01:59 <coremodule> #topic roll call
16:02:14 * pwhalen is here
16:02:45 <coremodule> Good morning pwhalen
16:02:57 <coremodule> Who is around for an IoT meeting?
16:06:20 <coremodule> IoT is looking good to my untrained eyes, we had a compose this morning that looks good in OpenQA
16:06:25 <coremodule> of F36
16:06:56 <coremodule> I ran yesterday's compose through the matrix and had no failures, everything looked good.
16:07:24 <coremodule> Should we close for lack of quorum?
16:07:25 <pwhalen> on hardware or in virt?
16:07:43 <pwhalen> yea, looks like it
16:07:50 <coremodule> Both hardware and virt
16:07:59 <coremodule> https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_36_RC_20220214.0_Summary?rd=Test_Results:Current_IoT_Summary
16:08:26 <coremodule> I do have a question about https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_36_RC_20220214.0_Summary?rd=Test_Results:Current_IoT_Summary#Hardware_Tests
16:09:00 <pwhalen> cool, question away :)
16:09:15 <coremodule> Do we want to update the Hardware Tests section of the matrix to reflect our Reference Platforms?
16:09:16 <coremodule> https://docs.fedoraproject.org/en-US/iot/reference-platforms/
16:09:42 * pbrobinson is here
16:09:44 <pwhalen> You da man now, I think I mentioned we should revisit that
16:09:45 <pbrobinson> sorry im late
16:09:52 <coremodule> no worries pbrobinson
16:10:10 <coremodule> Haha, alright, looks like it'll get updated
16:10:15 <coremodule> #topic 1) ==== Working Group process and admin  ====
16:10:16 <coremodule> #link https://docs.fedoraproject.org/en-US/iot/
16:10:24 <coremodule> We'll officially start since we have three
16:10:41 <coremodule> Anything for admin?
16:10:46 <pbrobinson> coremodule: how did you go with reviewing docs and your notes here, looking forward to PRs for docs updates
16:11:10 <coremodule> #info coremodule to update Hardware Tests on IoT test matrix
16:11:39 <coremodule> pbrobinson, I've got a rough draft of a release cycle page to put in the IoT docs, but haven't finished it yet
16:12:02 <coremodule> You'll be getting pr requests sometime soon
16:12:04 <coremodule> :)
16:12:30 <pbrobinson> cool, once you have it some of the way there we can also review it in the PR
16:13:20 <coremodule> Okay, I'll push it out and get your thoughts on what to add/how to change it
16:13:36 <pbrobinson> ultimately I'd like to move most of iot stuff in pagure over to the fedora-iot github so everything is in one place and that has better review/draft features
16:16:24 <coremodule> Something to look forward to in the future
16:16:47 <coremodule> once I'm a bit more settled in, that's something I can help with
16:17:22 <pbrobinson> I need to finish the move of tiaga data over to github too
16:17:47 <pbrobinson> a single place for people to find things will be a lot simplier
16:18:52 <coremodule> #topic 2) ==== Fedora 35 status ====
16:18:52 <coremodule> #info Fedora-IoT-35-20220112.0
16:18:52 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20220112.0&groupid=1&groupid=5
16:18:59 <coremodule> Anything for F35?
16:19:26 <pbrobinson> so we still look to have the anaconda bug that was apparently fixed
16:20:04 <pwhalen> Right
16:20:35 <pwhalen> coremodule: https://bugzilla.redhat.com/show_bug.cgi?id=2019579
16:20:39 <coremodule> thank you pwhalen
16:21:33 <pwhalen> koji task - https://koji.fedoraproject.org/koji/taskinfo?taskID=82813855
16:23:22 <coremodule> #info anaconda bug impacting F35 - https://bugzilla.redhat.com/show_bug.cgi?id=2019579
16:24:33 <pbrobinson> so once we have that properly fixed we can promote a compose to stable
16:24:39 <pwhalen> hrm, so this sounds more like the other bug
16:24:43 <pwhalen> https://bugzilla.redhat.com/show_bug.cgi?id=2018913
16:25:51 <pbrobinson> looking at the last comment there are we missing package?
16:27:11 <pbrobinson> or NVR we're waiting for, the dnf issues in the bug don't really affect us but we may need rpm-ostree to pull in a fix
16:27:52 <pwhalen> yea, we might be due to the package split by the sounds of it
16:32:04 <coremodule> #topic 3) ==== Fedora 36 status ====
16:32:04 <coremodule> #info Fedora-IoT-36-20220216.0
16:32:04 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220216.0&groupid=1&groupid=5
16:32:32 <coremodule> Fedora 36 IoT looks good, tested 20220214 yesterday, no issues
16:32:59 <pwhalen> this one - https://openqa.fedoraproject.org/tests/1132002#step/os_release/32
16:33:36 <pwhalen> usually its been behind at times, but shows the right format. For some reason its just showing up as f36
16:34:12 <pwhalen> PRETTY_NAME should be Fedora Linux 36.20220216.0 (IoT Edition Prerelease) and is Fedora Linux 36 (IoT Edition Prerelease)
16:34:43 <pbrobinson> something has changed in the fedora-release there I suspect
16:35:08 <pbrobinson> but I've not looked, it's generated automatically some how from available data
16:36:24 <coremodule> I can file a bug
16:37:11 <pbrobinson> or maybe the way ostree generates it, either way bug would be grand
16:37:47 <coremodule> okay, will do
16:38:20 <coremodule> #info os_release not showing correctly in F36: https://openqa.fedoraproject.org/tests/1132002#step/os_release/32
16:38:42 <coremodule> #topic 4) ==== Fedora 37/Rawhide status ====
16:38:50 <coremodule> Anything for F37/rawhide?
16:39:58 * pwhalen looks at why it failed
16:40:42 <pbrobinson> there's a change there and I need to dig into what ostree is doing there, it may make sense for us to change to the ostree bootcfg in f37
16:41:01 <pbrobinson> but that's ultimately a dev thingy
16:42:50 <pbrobinson> and sort of 36/7 cross over, still working on getting jetson nano booting for iot, not there yet but there's forward movement
16:43:02 <coremodule> that's positive!
16:43:40 <coremodule> #info pbrobinson working on getting Jetson Nano booting on IoT
16:47:29 <coremodule> #topic 5) ==== Open Floor ====
16:47:37 <coremodule> Anything for open floor? We had a long one today.
16:48:01 <pwhalen> nothing from me
16:48:50 <coremodule> thanks for coming pwhalen, pbrobinson
16:48:54 <coremodule> #endmeeting