16:00:49 <coremodule> #startmeeting Fedora IoT Working Group Meeting
16:00:49 <zodbot> Meeting started Wed Mar  9 16:00:49 2022 UTC.
16:00:49 <zodbot> This meeting is logged and archived in a public location.
16:00:49 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:49 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:49 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
16:00:50 <coremodule> #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule
16:00:50 <coremodule> #topic roll call
16:00:50 <zodbot> Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson
16:01:18 * pwhalen is here
16:01:21 <coremodule> hello everyone, who's around for an IoT meeting?
16:03:33 * pbrobinson is sort of o/
16:04:48 <coremodule> hi pwhalen, pbrobinson
16:04:50 <coremodule> #topic 1) ==== Working Group process and admin  ====
16:04:50 <coremodule> #link https://docs.fedoraproject.org/en-US/iot/
16:05:08 <coremodule> anything for admin?
16:05:23 <pwhalen> nothing from me
16:06:42 <coremodule> #info nothing for admin
16:06:50 <coremodule> #topic 2) ==== Fedora 35 status ====
16:06:50 <coremodule> #info Fedora-IoT-35-20220112.0
16:06:50 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20220112.0&groupid=1&groupid=5
16:06:56 <coremodule> moving to F35
16:07:23 <pwhalen> did we get a response on that systemd bug?
16:07:31 <coremodule> it seems this isn't building because of the systemd/resolv.conf bug
16:07:33 <coremodule> https://bugzilla.redhat.com/show_bug.cgi?id=2018913
16:07:49 <coremodule> but there has been no response from Zbigniew...
16:09:11 <coremodule> pwhalen, nothing yet...
16:09:26 <coremodule> It's been a week, I can try to ping him over email on the IoT list
16:10:56 <coremodule> his irc nick is zbyszek, I'll try to ping him on #fedora-devel first after the meeting
16:11:15 <coremodule> #info coremodule to get in touch with zbyszek about systemd bug
16:11:17 <pwhalen> maybe we need to open a new bug for our specific issue, and make it a prioritized bug
16:12:07 <pwhalen> it was reproducible when doing an f35 installation with updates on mainline
16:12:49 <coremodule> let me try talking to him after the meeting, if that doesn't go anywhere then I will do that
16:13:08 <pwhalen> coremodule++
16:13:12 <pwhalen> thanks
16:13:29 <coremodule> sure
16:13:34 <coremodule> alright, moving to f36
16:13:35 <coremodule> #topic 3) ==== Fedora 36 status ====
16:13:35 <coremodule> #info Fedora-IoT-36-20220302.0
16:13:35 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220309.0&groupid=1&groupid=5
16:14:41 <pwhalen> the failing zezere test on x86 I think is a result of the bios removal. It does pass on aarch64
16:14:58 <pwhalen> coremodule: did you get zezere working for you?
16:15:27 <coremodule> no, I haven't. I can't manually test this because it doesn't work for me...
16:15:53 <coremodule> pwhalen, if you get a chance, could you manually test this?
16:16:37 <coremodule> if not, I can see if sumantro can do it, I know he planned on doing some testing today
16:17:11 <pwhalen> yea, but we need to work out whats going wrong for you
16:18:13 <pwhalen> I saw an issue with zezere on armhfp, server issue
16:20:16 <coremodule> which image?
16:22:04 <pwhalen> f36 armhfp, doesnt seem to work with zezere. I'll file a bug today, likely just document using the arm-image-installer
16:22:15 <pwhalen> to copy the key
16:24:43 <coremodule> that sounds good
16:25:58 <coremodule> anything else for f36?
16:26:54 * pwhalen has nothing else
16:27:42 <coremodule> #topic 4) ==== Fedora 37/Rawhide status ====
16:27:43 <coremodule> #info Fedora-IoT-36-20220228.0
16:27:43 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220228.0&groupid=1&groupid=5
16:28:09 <coremodule> F37 has been failing compose, but I haven't looked into it too much with testing for F36
16:29:52 * pwhalen looks
16:30:24 <pwhalen> this task -> https://koji.fedoraproject.org/koji/taskinfo?taskID=83899740
16:31:20 <pwhalen> gi.repository.GLib.GError: g-io-error-quark: loading sysroot: No ostree= kernel argument found (0)
16:31:51 <pwhalen> we should open a bug there too
16:36:05 <coremodule> okay, I will do that too. pwhalen I will get with you after the meeting about filing this as a bug
16:37:39 <pwhalen> yea, sounds good
16:37:45 <coremodule> #topic 5) ==== Open Floor ====
16:37:51 <coremodule> anything for open floor? I have nothing
16:38:40 <pwhalen> I forgot to mention there is an issue with greenboot in f35
16:39:16 <pwhalen> greenboot-healthcheck  script tosses an error "Script '01_update_platforms_check.sh' FAILURE "
16:39:41 <coremodule> oh yeah, is that the failure that became apparent in #fedora-iot?
16:39:52 <pwhalen> that script checks to make sure it can reach the updates servers, it fails, but then it works when you run it manually
16:39:53 <pwhalen> yea
16:41:11 <pwhalen> I thought it was related to the systemd resolved change, but doesnt seem to be, same result using either. So maybe a timing issue?
16:41:20 <coremodule> is there a bug? I can file one if not. I need to reproduce locally
16:43:04 <pwhalen> not yet, should be as easy as updating in f35
16:43:29 <coremodule> just update f35 and it shows?
16:44:02 <pwhalen> right, update, reboot and you'll see it as you log in via ssh
16:44:14 <coremodule> okay, when I get a chance today, I will look at it
16:45:31 <pwhalen> thanks, I will assist where needed too
16:45:51 <coremodule> thanks pwhalen
16:45:58 <coremodule> if nothing else, we'll close in 5...
16:46:09 <coremodule> 4...
16:46:10 * pwhalen has nothing else
16:46:11 <coremodule> 3...
16:46:13 <coremodule> 2...
16:46:14 <coremodule> 1...
16:46:16 <coremodule> #endmeeting