15:00:51 #startmeeting Fedora IoT Working Group Meeting 15:00:51 Meeting started Wed Mar 24 15:00:51 2021 UTC. 15:00:51 This meeting is logged and archived in a public location. 15:00:51 The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:51 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:51 The meeting name has been set to 'fedora_iot_working_group_meeting' 15:00:51 #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule 15:00:51 Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson 15:00:51 #topic roll call 15:01:18 Good morning , who's here today? 15:01:50 * coremodule is here, good morning! 15:02:04 ahoj 15:02:12 bcotton: ahoj 15:02:21 bcotton: DST clash? 15:03:18 mhroncok: sort of. IoT moved their meeting a while back and now it overlaps 15:03:20 looks like it yes :) 15:03:33 it wasn't previously a problem 15:04:17 fedoora-meeting-1 is free, let's move the prioritized bugs meeting there 15:04:47 thanks bcotton 15:05:32 * pbrobinson is here 15:05:40 #topic 1) ==== Working Group process and admin ==== 15:05:41 #link https://docs.fedoraproject.org/en-US/iot/ 15:05:55 Anything for admin this week? 15:06:12 we need to go through and review the docs 15:06:19 other than that nothing of note 15:07:57 Right, someone pointed out some typos on the mailing list we should fix (if someone hasnt already) 15:08:34 #info Please look over the documentation for anything stale or needing corrections. 15:08:48 #topic 2) ==== Fedora 33 status ==== 15:09:08 Any new issues? 15:09:53 I looked into the reported "timeout" on the Raspberry Pi 2 from in channel, I couldnt reproduce but have seen the time outs on the Raspberry Pi 3 from time to time. 15:10:27 I've just used a loop to retry until it works, but should file a bug 15:10:47 its been a while since I hit it 15:10:49 new release synced out earlier in the week 15:11:02 what sort of timeout? 15:11:16 when running rpm-ostree commands 15:11:42 it happened more in f32, hasnt been a problem for me for a while 15:12:19 it could be the mSD card, network, a number of user specific criteria, these things are very hard to align to a specific issue sadly 15:12:49 right, I've not hit on more capable hardware 15:13:14 Anything else for F33? 15:14:19 #topic 3) ==== Fedora 34 status ==== 15:14:29 #info Fedora 34 IoT Beta released yesterday! 15:14:29 #link https://getfedora.org/iot/download/ 15:14:46 there's an issue with grub2, should be fixed in today's compose 15:15:17 #info grub2-mkconfig -o /boot/grub2/grub.cfg breaks grub 15:15:17 #link https://bugzilla.redhat.com/show_bug.cgi?id=1940524 15:15:34 I added a note to common bugs 15:15:40 #info Added to common bugs - https://fedoraproject.org/wiki/Common_F34_bugs#IoT_Edition 15:15:46 feel free to edit 15:16:03 Likely should be included in the overall distro as I saw other hitting it last night 15:17:22 pbrobinson also mentioned we should have a new parsec build soon to fix the long standing service failure 15:17:41 #info Fedora-IoT-34-20210321.0 15:17:41 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=34&build=Fedora-IoT-34-20210321.0&groupid=1&groupid=5 15:18:39 The aarch64 failures can be ignored, there is a workaround in openqa that tries to dnf install plymouth 15:18:54 which of course fails on ostree 15:19:04 Has anyone else hit issues not yet reported? 15:20:21 #topic 4) ==== Fedora 35 (Rawhide) status ==== 15:20:29 none here 15:20:35 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20210322.0&groupid=1&groupid=5 15:21:39 a few failures that need investigation on aarch64. Odd that the release_identification test fails only on aarch64 15:23:41 Anything else for F35? 15:24:59 #topic 5) ==== Open Floor ==== 15:25:03 * jsmith apologizes for being late 15:25:37 np :) 15:25:42 anything else for today? 15:27:33 #endmeeting