15:01:54 <coremodule> #startmeeting Fedora IoT Working Group Meeting
15:01:54 <zodbot> Meeting started Wed Mar 30 15:01:54 2022 UTC.
15:01:54 <zodbot> This meeting is logged and archived in a public location.
15:01:54 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:01:54 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:54 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
15:01:54 <coremodule> #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule
15:01:54 <coremodule> #topic roll call
15:01:54 <zodbot> Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson
15:02:06 <coremodule> Good morning everyone, who is around for an IoT meeting today?
15:02:07 * pwhalen is here
15:02:11 <coremodule> hi pwhalen
15:02:12 <pwhalen> Good morning
15:03:09 <bcotton> .hello2
15:03:10 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
15:03:24 <coremodule> hi bcotton
15:04:12 <coremodule> #topic 1) ==== Working Group process and admin  ====
15:04:12 <coremodule> #link https://docs.fedoraproject.org/en-US/iot/
15:04:28 * pbrobinson is late
15:04:47 <coremodule> #info Next Wednesday, April 6th will be an F36 IoT test day
15:04:56 <coremodule> #info https://fedoraproject.org/wiki/Test_Day:2022-04-06_Fedora_36_IoT_Edition
15:05:07 <coremodule> hi pbrobinson
15:05:17 * pbrobinson is looking for a few links
15:05:25 * bcotton has a topic w/r/t docs (https://pagure.io/fedora-iot/iot-docs/issue/83) not sure if it belongs here or later
15:06:18 <pbrobinson> bcotton: here, that's the link I was looking for
15:06:24 <pbrobinson> bcotton: go for it
15:06:40 <bcotton> cool
15:06:41 <coremodule> +1
15:07:16 <bcotton> so the Docs team, which I am in the process of de-zombie-ing, wants to have Teams split their internal docs from their user-facing docs
15:07:32 <bcotton> i'm happy to do an initial split
15:07:51 <bcotton> peter mentioned moving docs to github, which seems well-timed
15:07:54 <pbrobinson> I am very excited for this especially with someone else taking the lead :)
15:08:30 <bcotton> so what i'm thinking is once the github repo is set up and imported from the existing pagure docs, i'll work on that in the background and submit a PR for the team to review
15:08:51 <bcotton> then when we're all happy, we can adjust the docs build system to pull from github and remove the pagure repo
15:09:21 <pbrobinson> bcotton++ sounds good to me, so I can do that whenever, it's not high change so easy enough to sync up
15:09:21 <zodbot> pbrobinson: Karma for bcotton changed to 10 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:09:22 <pwhalen> sounds good to me, thanks bcotton
15:09:37 <pwhalen> bcotton++
15:09:37 <zodbot> pwhalen: Karma for bcotton changed to 11 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:09:50 <bcotton> this means we can do the work transparently and not impact users as we play around with it. the downside is that any changes that get made in pagure would have to be replicated in github post-split
15:10:29 <pbrobinson> right, it's not a high change repo so that's easy enough to do I believe
15:10:37 <bcotton> pbrobinson: sounds good! just let me know when the repo is ready and i'll get to work on it. you can add my github account (@funnelfiasco) or I can just make PRs from a fork, whichever works for you
15:10:53 <bcotton> yeah, it doesn't seem like it would be a huge burden :-)
15:11:10 <pbrobinson> bcotton: I'll add you to the repo, I think that's least friction all around
15:11:25 <bcotton> wfm
15:11:49 <coremodule> thanks bcotton, this will be a good change
15:12:30 <pbrobinson> I have one other admin topic, not sure if coremodule wants to info or tag any of these notes up
15:13:02 <coremodule> go for it pbrobinson, I can do it while you add your topic
15:13:39 <coremodule> #info Docs team headed by bcotton in the process of splitting IoT users docs from IoT contributors docs
15:14:02 <pbrobinson> #link https://pagure.io/fedora-iot/iot-docs/issue/83
15:14:36 <pbrobinson> #action pbrobinson to setup the github repo, mirror the existing docs repo and grant bcotton access
15:15:13 <pbrobinson> #info fedora outreachy project for IoT
15:15:19 <pbrobinson> #link https://pagure.io/mentored-projects/issue/127
15:16:14 <pbrobinson> Last minute at the request of someone I submitted a outreachy intern project, hence why there's been a number of introduction emails to the iot list
15:16:43 <pbrobinson> it will tie in with a Fedora change or two (more on those in F-37 section)
15:17:13 <pbrobinson> Myself and Antonio (runcom) plus some of my team will mentor
15:17:36 <pbrobinson> that's it really
15:18:22 <coremodule> cool, when is it planned to begin?
15:19:24 <pbrobinson> #info details on the site https://www.outreachy.org/ but it basically runs from May 30 to end of August
15:21:28 <coremodule> alright, sounds good
15:21:30 <coremodule> #topic 2) ==== Fedora 35 status ====
15:21:31 <coremodule> #info Fedora-IoT-35-20220112.0
15:21:31 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20220112.0&groupid=1&groupid=5
15:22:26 <coremodule> I went for a hail-Mary here and tried contacting Zbigniew one last time over direct email to see about building the systemd fix for this, but didn't hear back. I'll submit a specific prioritized bug this week.
15:22:26 <pbrobinson> there's been updates running, but the final stage is still broken :-/
15:22:40 <pbrobinson> OK, thanks
15:22:57 <pwhalen> thanks coremodule, not sure what else we can do
15:23:22 <coremodule> #action coremodule to submit prioritized bug for systemd fix for this
15:23:45 <coremodule> #topic 3) ==== Fedora 36 status ====
15:23:45 <coremodule> #info Fedora-IoT-36-20220326.0
15:23:45 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220326.0&groupid=1&groupid=5
15:24:07 <coremodule> The clevis test is failing, but I manually tested this morning and it worked fine, must be a needle issue...
15:24:56 <coremodule> sumantro was going to test Zezere last week, never heard from him, I will reach out and see what he found.
15:24:59 <pwhalen> coremodule: its never worked on aarch64
15:25:23 <coremodule> ah, good, because I tested on x86_64 this morning :)
15:25:38 <coremodule> didn't notice until you said that
15:27:35 <pwhalen> that might have changed since I last looked, its been a while
15:27:47 <pbrobinson> overall I think we're mostly OK here besides the ostree issue
15:28:59 <pwhalen> coremodule: there is an issue with recent compose attempts
15:29:18 * coremodule looking
15:31:45 <coremodule> pbrobinson, is this the ostree issue you mentioned?
15:32:02 <pwhalen> coremodule: https://github.com/coreos/rpm-ostree/pull/3535
15:32:21 <pwhalen> iot compose - https://koji.fedoraproject.org/koji/taskinfo?taskID=84835482
15:33:26 <coremodule> okay, I'll look into it after the meeting
15:34:18 <coremodule> #topic 4) ==== Fedora 37/Rawhide status ====
15:34:19 <coremodule> #info Fedora-IoT-36-20220327.0
15:34:19 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220327.0&groupid=1&groupid=5
15:35:02 <pwhalen> sorry,  missed the topic change, that bug should be fixed in the latest version of rpm-ostree
15:35:04 <pbrobinson> I suspect you meant a 37 release there
15:35:29 <coremodule> ah yeah, let me fix it
15:35:35 <coremodule> #undo
15:35:35 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x7f6a38d32080>
15:35:38 <coremodule> #undo
15:35:38 <zodbot> Removing item from minutes: INFO by coremodule at 15:34:19 : Fedora-IoT-36-20220327.0
15:36:02 <coremodule> #info Fedora-IoT-37-20220327.0
15:36:02 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220327.0&groupid=1&groupid=5
15:36:24 <pbrobinson> there's a new parsec 1.0 build inbound for both f36/f37, there's a few more fixes we need there pre freeze
15:37:32 <coremodule> #info new parsec build inbound for both f36 and f37
15:40:36 <pbrobinson> #info fedora IoT features for F-37
15:40:45 <pbrobinson> #link https://fedoraproject.org/wiki/Changes/FIDODeviceOnboarding
15:41:06 <pbrobinson> this feature is independent but a dependency of the outreachy project mentioned earlier
15:41:19 <pbrobinson> #link https://fedoraproject.org/wiki/Changes/IoTArtifactsWithOSBuild
15:41:21 <pwhalen> f37 failed with what looks to be an infra issue, 502 error - https://koji.fedoraproject.org/koji/taskinfo?taskID=84835482
15:41:42 <pbrobinson> pwhalen: and mainline has failed since due to grub issues
15:41:53 <pbrobinson> I think it should be good again tomorrow
15:41:56 <pwhalen> ah
15:45:54 <coremodule> #topic 5) ==== Open Floor ====
15:45:58 <pwhalen> sorry, looks like the f36 failure is different with yesterdays compose
15:46:03 <pwhalen> I didnt notice it
15:46:20 <pwhalen> failed with 'loading sysroot: No ostree= kernel argument found'
15:46:37 <coremodule> that's what I was seeing too, it looks like there are some garbage directories in the compose folder?
15:46:39 <pwhalen> https://koji.fedoraproject.org/koji/taskinfo?taskID=84907559
15:47:36 <pwhalen> coremodule: garbage directories?
15:47:54 <coremodule> https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-36-20220330.0/
15:48:01 <coremodule> those tmp directories?
15:49:26 <pbrobinson> so with the features there will be some more in the coming weeks, but those two are what I have to date
15:49:45 <pwhalen> looks like an issue with todays compose.
15:50:12 <pwhalen> running the git checkout Failed to connect to pagure.io port 443: Connection refused
15:50:29 <pwhalen> coremodule: we can discuss out of the meeting
15:50:56 <coremodule> pbrobinson, sounds good, the FIDO initiative sounds like it'll be a good addition to IoT
15:50:58 <coremodule> alright
15:51:04 <coremodule> thanks for coming this week
15:51:16 <coremodule> #endmeeting