15:01:40 #startmeeting Fedora IoT Working Group Meeting 15:01:40 Meeting started Wed Apr 27 15:01:40 2022 UTC. 15:01:40 This meeting is logged and archived in a public location. 15:01:40 The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:01:40 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:40 The meeting name has been set to 'fedora_iot_working_group_meeting' 15:01:41 #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule 15:01:41 Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson 15:01:41 #topic roll call 15:01:51 Hi everyone, who's around for an IoT meeting today? 15:01:58 * pwhalen is here 15:03:15 .hello2 15:03:16 bcotton: bcotton 'Ben Cotton' 15:03:51 hi pwhalen, bcotton 15:04:26 good morning 15:04:39 #topic 1) ==== Working Group process and admin  ==== 15:04:39 #link https://docs.fedoraproject.org/en-US/iot/ 15:05:13 Anything for docs or admin? 15:06:30 I'm doing some clean up on the docs now 15:07:19 #info pwhalen is currently cleaning up the IoT docs 15:07:44 the split user and WG docs are now live 15:07:55 bcotton++ 15:07:57 #info the split user and WG docs are now live 15:08:02 bcotton++ 15:08:05 thanks again for working on that 15:08:32 happy to help. it was less involved than i worried it'd be :-) 15:10:36 #topic 2) ==== Fedora 35 status ==== 15:10:36 #info Fedora-IoT-35-20220112.0 15:10:36 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20220112.0&groupid=1&groupid=5 15:10:52 Nothing has changed here, and to be honest, I haven't looked at it. 15:10:55 Still looks the same :) 15:11:07 But I do know the problem still exists! 15:11:11 hah. 15:11:19 Yesterday some internal folks were having issues installing Fedora 35 because of this issue. 15:11:36 Not IoT specific. Sure would be nice to have it fixed. 15:12:15 Do you know what they were trying to install? 15:12:24 The last attempt to fix it in systemd is in updates.. still doesnt work 15:12:46 F35 aarch64 with updates. But it also affects x86 too. 15:14:01 At this point, as long as the upgrade to F36 works 15:14:34 there has to be a half dozen bugs on it 15:14:39 perhaps more 15:15:14 this confirms the latest fix, doesnt work - https://bugzilla.redhat.com/show_bug.cgi?id=2074083 15:16:07 #info the bug that is causing this issue is more widespread than just IoT 15:16:19 #link https://bugzilla.redhat.com/show_bug.cgi?id=2074083 15:17:24 #info the latest attempt at a fix doesn't fix the issue 15:18:09 thanks for the info pwhalen. I didn't know this was bigger than IoT 15:20:22 #topic 3) ==== Fedora 36 status ==== 15:20:22 #info Fedora-IoT-36-20220425.0 15:20:22 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220425.0&groupid=1&groupid=5 15:20:42 nice, looks good 15:21:18 I am not seeing the images, just the iso... wonder if it's still composing 15:21:18 I think we intended this to be the GA, but I guess there might be another rc? 15:21:19 * coremodule looks 15:23:08 hrm, right.. looks like its still running 15:23:13 https://koji.fedoraproject.org/koji/taskinfo?taskID=86241287 15:23:19 images are done 15:24:52 oh good, okay. 15:25:02 #info F36 is looking good and on-track 15:25:10 it shouldnt be running still though 15:25:37 I guess I don't see where it's still running, only that it's completed the tasks and the state is now "closed" 15:26:13 Oh, or it's still running because the images aren't there, but the task says it's done? 15:27:10 I'm looking at the 26th 15:28:38 25th the images are there, I think yesterdays is hung up 15:30:02 yeah, the last thing I see is: 15:30:03 Writing image-build config for IoT.aarch64-armhfp-x86_64 into /mnt/koji/compose/iot/Fedora-IoT-36-20220426.0/work/image-build/IoT/raw-xz_Fedora-IoT_aarch64-armhfp-x86_64.cfg 15:30:12 for the 26th 15:31:42 No worries, I'll pester Peter tomorrow about it 15:31:59 are you good to do that? I can file a bug if it helps... 15:32:16 or pester him myself to keep you from having to do it 15:32:20 a bug on the compose? No worries.. 15:32:31 I might have already pestered 15:32:33 yeah, i mean, just to document it... 15:32:49 I don't know exactly what it'd include other than "compose is stuck, see this log" 15:33:11 Yea, easier to just ping, which I did 15:33:34 cool, okay. thanks. 15:33:36 pwhalen++ 15:33:48 #topic 4) ==== Fedora 37/Rawhide status ==== 15:33:49 #info Fedora-IoT-37-20220426.0 15:33:49 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220426.0&groupid=1&groupid=5 15:34:20 One day we'll figure out that versioning issue 15:34:41 its only one day off 15:34:45 I wonder why... 15:35:02 and only arm64 15:36:24 well, other than that, it all looks good 15:37:00 Agreed, surprising good 15:37:35 #topic 5) ==== Open Floor ==== 15:38:00 I'm sure you did see, but we did spin an RC1.2. But all the results that don't have to do with gtk will transfer 100% 15:38:12 rc3? 15:38:32 There are more gnome issues, with enough votes 15:38:40 or, were those fixed in 1.2? 15:39:27 https://qa.fedoraproject.org/blockerbugs/milestone/36/final/buglist 15:40:09 no, these weren't fixed in 1.2 15:40:23 so yeah, maybe a 1.3, maybe we waive them and go with 1.2... I'm not sure. 15:40:52 looks like there's some juicy conversation going on in #fedora-qa 15:40:55 Ok, a cliffhanger to be determined tomorrow 15:41:24 right! hah. 15:41:38 alright, I'll close here and we can talk in PM or in-channel 15:41:47 thanks for coming pwhalen and bcotton 15:41:49 #endmeeting