15:02:29 #startmeeting Fedora IoT Working Group Meeting 15:02:29 Meeting started Wed Aug 31 15:02:29 2022 UTC. 15:02:29 This meeting is logged and archived in a public location. 15:02:29 The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:02:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:29 The meeting name has been set to 'fedora_iot_working_group_meeting' 15:02:29 #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule 15:02:29 Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson 15:02:29 #topic roll call 15:02:37 sorry for the late start 15:02:42 * pwhalen is here 15:02:42 who is around today for an IoT meeting? 15:02:53 hey pwhalen, how are you this week? 15:02:54 How're you doing coremodule? 15:03:20 Doing ok today, thanks :D 15:03:39 I'm good here, wonder about a date for an IoT test day... but we can get to that 15:05:48 how has the start of the new school year been for you/your wife/your kids? 15:08:21 School starts next week here, so still in preparation mode 15:08:41 well, I realize we dont have quorum today, but lets do quick recap of things 15:08:49 sure 15:08:56 looking at f37 and f38, it looks like we have builds that aren't failing 15:09:02 https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220831.0&groupid=1&groupid=5 15:09:08 https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=38&build=Fedora-IoT-38-20220830.0&groupid=1&groupid=5 15:09:47 https://bugzilla.redhat.com/show_bug.cgi?id=2121944 15:10:00 Is the remaining bug 15:10:35 I know this is being looked at. it was accepted as both a final blocker and a beta FE 15:10:42 so hopefully we should have a fix soon 15:11:13 who is looking at it? 15:12:08 It would be great to get some of the audit messages cleaned up, would you be able to file some bugs on those? 15:12:47 i don't know who is looking at it, but that it was a hot topic at the meeting 15:12:52 so perhaps I spoke too soon 15:13:05 yeah, I can look into them today and see what I can file 15:13:19 * pbrobinson is here 15:13:22 ok, I was lookig this morning and just dont want to duplicate :) 15:15:07 sounds good to me! 15:15:55 is there any preference regarding date for an IoT test day/week? 15:16:26 coremodule: we have a quorum with pbrobinson here, lets go through everything 15:16:57 okay 15:16:58 sorry I was late, was yelling a PRs 15:16:59 #topic 1) ==== Working Group process and admin  ==== 15:16:59 #link https://docs.fedoraproject.org/en-US/iot/ 15:17:10 no worries pbrobinson 15:17:28 anything to discuss for docs/admin? 15:17:57 * pwhalen has nothing for today 15:18:07 we will no doubt need to update docs some 15:19:36 #info Docs could use going through and updating. 15:19:57 Did we ever have any interns look at the docs? I know there was talk about it near the launch of f36 timeframe 15:20:02 Right, lets try to make a point to look at them this week 15:21:53 none I'me aware of 15:21:53 Alright, on to F36 15:21:59 #topic 2) ==== Fedora 36 status ==== 15:22:00 #info Fedora-IoT-36-20220718.0 15:22:00 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220718.0&groupid=1&groupid=5 15:22:32 is this still failing on the armhfp disk image? 15:23:13 it looks like armhfp and aarch64. neither have a disk image, only iso 15:23:20 at a quick glance 15:23:26 looks like yes -https://koji.fedoraproject.org/koji/taskinfo?taskID=91429683 15:23:52 so aarch64 looks fine 15:24:29 the armhfp looks like it's missing an anaconda stage two but I'm not sure why it's failing on that because it shouldn't have changed since apr GA of F-36 15:24:56 armhfp drops to dracut, I think this might be the same issue Kevin had with the date? 15:25:02 it would be great if someone could dig into that as I've had some requests from arm partners for an updated image 15:25:18 https://koji.fedoraproject.org/koji/taskinfo?taskID=91429683 15:25:40 the screenshot says about missing stage 2 15:25:58 Right, I think it cant pull it down because of the date 15:26:43 so coremodule can you take a look at that? 15:26:59 I can look and file a bug, see what I can get done there 15:28:20 I think its this - https://bugzilla.redhat.com/show_bug.cgi?id=2077680 15:29:13 ahhh, thanks pwhalen 15:29:36 i will do what I can to confirm and either add a new bug or report there 15:29:42 probably a new bug honestlyt 15:30:39 okay, on to F37 15:30:40 #topic 3) ==== Fedora 37 status ==== 15:30:41 #info Fedora-IoT-37-20220831.0 15:30:41 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220831.0&groupid=1&groupid=5 15:30:47 yea might be, I dont see the complaint about the cert, but could just be further up or network in general or something 15:30:53 most things are fixed up now 15:31:23 we're a bit late on the osbuild stuff but we're still planning on landing that for f37 in the next day or so 15:31:49 oh, looks like aarch64 isnt happy, I looked at x86 this morning and thought it was better 15:34:35 yeah, I can try to rerun the tests and see what happens 15:35:35 #info We are waiting on the osbuild bits, but they should land later this week. 15:36:12 #topic 4) ==== Fedora 38/Rawhide status ==== 15:36:12 #info Fedora-IoT-38-20220822.0 15:36:12 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=38&build=Fedora-IoT-38-20220830.0&groupid=1&groupid=5 15:37:14 Looks similar, display output issues at times in openqa 15:38:33 sorry, thats the clevis test, which needs to be fixed for aarch64. Otherwise its the same failing service and the os-release issue we've had for a while 15:45:04 alright 15:45:11 anything else for f38? 15:45:44 nothing else from me 15:45:49 we'll have some more features incoming soon for f38 15:46:05 but when they're submitted I'll mention them here 15:46:14 so we should have corresponding tests in openqa too 15:46:14 that's it for me 15:46:37 that sounds good pbrobinson. excited to see what comes 15:46:54 pwhalen, good thinking 15:47:01 some of the overflow the team didn't get to for f37 15:47:20 using the signed rpm feature higher up in the OS etc 15:49:37 #topic 5) ==== Open Floor ==== 15:49:40 F37 aarch64 looks better after the rerun, thanks coremodule 15:50:11 oh good, that's always nice when that works out that way 15:50:46 rebase still doesnt have display output though, not sure why 15:50:46 I just wanted to get your thoughts on a date for an IoT test day/week. Before or after Beta? 15:51:15 pwhalen, oh yeah, i see that 15:51:33 We should likely do it before beta,I like test weeks to allow for more results 15:52:01 when is beta? 15:52:35 I believe in two weeks 15:52:45 Tue 2022-09-13: Beta release (early target date) 15:53:16 hmm, so maybe we can run the testweek the week of beta? 15:53:26 its close, maybe we wait til after beta? 15:53:33 we might now make that milestone either, looking at the accepted blockers we currently have 11 15:53:44 ouch 15:53:52 *we might not 15:55:24 let me suggest to sumantro the week of Sept. 12 and see what he says. 15:56:20 oh, I was way off on the blockers. theres 11 final blockers but only 1 beta blocker 15:56:26 I think we found most people focused on beta testing, so maybe we wait til after beta and allow for more time for the osbuild issues to be resolved 15:56:43 I'm okay with that, actually prefer that idea to be honest 15:56:48 sold 15:56:57 boom, okay, I'll let Sumantro know 15:57:04 thanks 15:57:11 anything else for todays meeting? don't remember the last time we used all our alloted time 15:57:21 * pwhalen has nothing else 15:58:00 thanks for attending you two 15:58:05 let's end for now 15:58:16 #endmeeting