16:00:01 <coremodule> #startmeeting Fedora IoT Working Group Meeting
16:00:01 <zodbot> Meeting started Wed Mar 23 16:00:01 2022 UTC.
16:00:01 <zodbot> This meeting is logged and archived in a public location.
16:00:01 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:01 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
16:00:01 <coremodule> #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule
16:00:01 <coremodule> #topic roll call
16:00:01 <zodbot> Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson
16:00:09 <coremodule> hi everyone, who's around for an IoT meeting?
16:01:51 * pwhalen is here
16:02:52 <sumantro> /me is here
16:02:55 * sumantro is here
16:03:21 * pwhalen high fives sumantro
16:03:59 <coremodule> hi pwhalen
16:04:01 <coremodule> hi sumantro
16:04:07 <coremodule> let's get started
16:04:13 <coremodule> #topic 1) ==== Working Group process and admin  ====
16:04:13 <coremodule> #link https://docs.fedoraproject.org/en-US/iot/
16:04:56 <coremodule> sumantro and I were talking about hosting an IoT test day on Wednesday, April 6th... does this date work for you pwhalen?
16:06:34 <pwhalen> Yea, that works for me.
16:06:50 <coremodule> cool.
16:07:09 <coremodule> #info Fedora IoT test day will be scheduled for two weeks from today, Wed., April 6th
16:07:09 <sumantro> thanks pwhalen and coremodule :)
16:07:59 <coremodule> sumantro, I'll update the pagure bug and we can go from there. next week we can discuss which image at that time we think we should use as our test image.
16:08:13 <coremodule> since it'll be a little closer to the date
16:09:10 <sumantro> coremodule, copied
16:09:51 <coremodule> pwhalen, I also wanted to talk about the time of this meeting, should we make it an hour before like it was before the time change or leave it as-is?
16:11:24 <sumantro> pwhalen, high fives :D
16:11:39 <pwhalen> coremodule: we should move it back for next week. I think everyone changes this weekend
16:11:45 <pwhalen> time wise
16:11:50 <coremodule> gotcha
16:12:21 <coremodule> I will change the email that gets sent out to reflect the time change
16:13:05 <pwhalen> thanks
16:13:25 <coremodule> #topic 2) ==== Fedora 35 status ====
16:13:25 <coremodule> #info Fedora-IoT-35-20220112.0
16:13:25 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20220112.0&groupid=1&groupid=5
16:13:34 <pwhalen> Any response on that bug?
16:13:42 <pwhalen> I dont think I saw one
16:13:57 <coremodule> I tried to get a hold of Zbigniew on IRC a week ago, never heard anything. There hasn't been any movement on the bug...
16:14:15 <coremodule> https://bugzilla.redhat.com/show_bug.cgi?id=2018913
16:16:10 <pwhalen> Perhaps we should open a new bug with our issue, make it prioritized?
16:16:12 <coremodule> I guess I could send an email out to the IoT list and ask Zbigniew there?
16:16:37 <coremodule> pwhalen, yeah, probably the best idea.
16:16:42 <coremodule> I'll do that after the meeting.
16:17:34 <coremodule> #topic 3) ==== Fedora 36 status ====
16:17:34 <coremodule> #info Fedora-IoT-36-20220320.0
16:17:34 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220320.0&groupid=1&groupid=5
16:19:05 <coremodule> it looks like the zezere test does work..?
16:20:09 <pwhalen> Not sure why its failing on aarch64 there
16:21:36 <pwhalen> I tested upgrades from F35->36 yesterday. Everything worked ok, but a number of packages were downgraded
16:21:40 <pwhalen> https://paste.centos.org/view/26ca2d2b
16:21:46 <coremodule> looks like it started between 20220306 and 20220308
16:22:06 <pwhalen> big one was - rpm-ostree 2022.5-1.fc35 -> 2022.2-1.fc36
16:22:24 <pwhalen> The newer should be in the next compose
16:23:43 <pwhalen> I just restarted that task to see if its any different
16:26:14 <coremodule> Okay, cool. Guess we'll see.
16:26:54 <pwhalen> The test is great, but we should be testing what people actually use
16:27:16 <pwhalen> which is a problem for you coremodule, not sure whats going on there. sumantro have you tried?
16:27:39 <coremodule> I think he disconnected. I'll ask him over telegram
16:27:47 <pwhalen> looks like hes gone
16:27:53 <pwhalen> thanks
16:29:46 <coremodule> okay, he says he's going to test it
16:29:50 <coremodule> and post to the matrix
16:30:06 <coremodule> let's move on and we can see if the test completes while we're on 37
16:30:13 <coremodule> since it's just you and me now, hah
16:30:25 <coremodule> #topic 4) ==== Fedora 37/Rawhide status ====
16:30:25 <coremodule> #info Fedora-IoT-36-20220228.0
16:30:25 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220228.0&groupid=1&groupid=5
16:30:38 <coremodule> I haven't actually looked at Rawhide IoT in a while, this is my bad
16:30:49 <pwhalen> completely understandable
16:31:06 <coremodule> I will look into the logs today and get a bug filed and hopefully we can start getting some IoT 37 composes
16:31:21 <coremodule> s/today/this week
16:31:23 <pwhalen> looks like a needle issue
16:31:45 <pwhalen> https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_36_RC_20220318.0_Summary
16:31:49 <pwhalen> oops
16:31:56 <pwhalen> https://openqa.fedoraproject.org/tests/1152937#step/_do_install_and_reboot/1
16:33:02 <coremodule> is this that bios/uefi issue we had a few weeks ago?
16:33:38 <pwhalen> https://openqa.fedoraproject.org/tests/1152937#step/_do_install_and_reboot/16
16:33:58 <pwhalen> that looks like it, might be using the old bios setup in rawhide
16:34:13 <coremodule> looks like it. I'll ping adamw and see if he can help out...
16:35:18 <coremodule> anything else for f37?
16:35:35 <pwhalen> no from m e
16:35:39 <coremodule> #topic 5) ==== Open Floor ====
16:35:51 <coremodule> thanks for always showing up pwhalen
16:36:54 <coremodule> #endmeeting