15:01:04 <coremodule> #startmeeting Fedora IoT Working Group Meeting
15:01:04 <zodbot> Meeting started Wed Apr 20 15:01:04 2022 UTC.
15:01:04 <zodbot> This meeting is logged and archived in a public location.
15:01:04 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:01:04 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:04 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
15:01:04 <coremodule> #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule
15:01:04 <zodbot> Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson
15:01:04 <coremodule> #topic roll call
15:01:16 * pwhalen is here
15:01:17 <coremodule> Good morning everyone, who is around for an IoT meeting?
15:01:23 <pwhalen> Good morning!
15:01:26 <bcotton> .hello2
15:01:27 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
15:02:31 <coremodule> Hi pwhalen and bcotton
15:03:24 <coremodule> let's get started
15:03:29 <coremodule> #topic 1) ==== Working Group process and admin  ====
15:03:29 <coremodule> #link https://docs.fedoraproject.org/en-US/iot/
15:04:13 * bcotton has docs update!
15:04:18 <coremodule> take it away!
15:04:49 <bcotton> #info User and WG docs are split on the stage server
15:04:51 <bcotton> #link https://docs.stg.fedoraproject.org/en-US/iot-wg/
15:04:54 <bcotton> #link https://docs.stg.fedoraproject.org/en-US/iot/
15:05:08 <pwhalen> bcotton++
15:05:23 <bcotton> If no one sees any problems with that, i'll update the production docs config
15:05:25 <coremodule> Wow, thanks bcotton, this looks great
15:06:04 <bcotton> there's still the open question of if we're using https://pagure.io/fedora-iot/issues for general issue reporting/work planning or if that's moved to a GitHub repo, too
15:06:45 <bcotton> i didn't edit content much, but i did make a few edits where it made sense to split or the wording was...suboptimal :-)
15:07:47 <pwhalen> I don't think we currently use github, most issues are reported in Bugzilla
15:07:55 <coremodule> funnily enough, after you brought up if we want to continue using pagure for issues reporting last meeting, we had an issue reported there... not that it means anything, hah.
15:08:20 <bcotton> leave it to dusty ;-)
15:08:52 <bcotton> but yeah, it looks like two of the issues in that pagure repo have been modified in the last year (one open, one closed)
15:09:12 <bcotton> so if we want to direct folks to Bugzilla, that works for me, too
15:09:23 <bcotton> most of the open issues look like things that should be BZs anyway
15:10:00 <pwhalen> right, I only use bugzilla to report issues myself
15:10:50 <coremodule> me too
15:11:26 <bcotton> okay, so i'll update the docs to point to BZ and leave cleanup/decomissioning of the pagure repo for a later date?
15:11:55 <pwhalen> wfm, lets talk about again when pbrobinson is back, he may have a preference
15:12:08 <coremodule> +1 to that
15:12:51 <bcotton> #agreed the Docs should refer folks to BZ for reporting issues. we'll leave how to cleanup/decomission the pagure repo for later
15:13:01 <bcotton> awesome. i'll make those edits shortly
15:13:03 <bcotton> that's all i have
15:13:49 <coremodule> here's the tracker bug for IoT:
15:13:49 <coremodule> https://bugzilla.redhat.com/show_bug.cgi?id=1269538
15:14:02 <coremodule> if you wanted to add that to the doc where it refers folks to BZ
15:14:28 <pwhalen> good call coremodule
15:15:31 <coremodule> I did just want to mention the tentative hostname change proposal that dustymabe made last week, pwhalen I know you saw it already, but I'll add it here for the meeting log
15:15:35 <coremodule> #info Please comment on the default hostname change issue that dustymabe suggested last meeting
15:15:35 <coremodule> #link https://pagure.io/fedora-iot/issue/49
15:15:59 <bcotton> good point. i'll add a link to the IoT component with a "if you know which component to file against, set your bug to block the tracker"
15:16:16 <bcotton> (or maybe the other way around, but... yes)
15:16:46 <coremodule> that sounds great to me bcotton
15:17:27 <coremodule> #topic 2) ==== Fedora 35 status ====
15:17:27 <coremodule> #info Fedora-IoT-35-20220112.0
15:17:27 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20220112.0&groupid=1&groupid=5
15:18:02 <coremodule> I haven't looked at this since last meeting... I was kinda hoping we'd have an F36 release sooner rather than later and this would all magically disappear...
15:18:11 <pwhalen> right, heh
15:18:29 <bcotton> :-(
15:18:30 <pwhalen> I'l check upgrades still work
15:18:45 <bcotton> 0/2 on on-time releases since i was promoted to principal :-)
15:19:18 <pwhalen> its done when its done.
15:19:51 <coremodule> lol! right, what pwhalen said. we'll get there.
15:22:35 <pwhalen> shall we move on? Not much to say about this F35 myself
15:22:54 <coremodule> yeah, sorry
15:22:55 <coremodule> #topic 3) ==== Fedora 36 status ====
15:22:55 <coremodule> #info Fedora-IoT-36-20220418.0
15:22:55 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220418.0&groupid=1&groupid=5
15:23:09 <coremodule> this looks good to me!
15:23:14 <pwhalen> Looks good
15:24:02 <pwhalen> coremodule: is someone else in QE able to do the zezere testing?
15:24:37 <coremodule> sumantro said he would cover that, I will ping him and ask him to test this latest set on the matrix
15:25:24 <pwhalen> thanks!
15:25:32 <coremodule> #topic 4) ==== Fedora 37/Rawhide status ====
15:25:32 <coremodule> #info Fedora-IoT-37-20220417.0
15:25:32 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220417.0&groupid=1&groupid=5
15:25:48 <coremodule> 37 is also looking good
15:26:14 <pwhalen> I broke rawhide for a bit there, compose was fine but naming was a mess
15:26:35 <pwhalen> we ended up with - https://kojipkgs.fedoraproject.org/compose/iot/Fedora-37-20220413.0/
15:26:44 <pwhalen> no IoT in the compose name
15:27:12 <coremodule> oh now I see it
15:27:31 <pwhalen> I was trying to fix the double IoT in the iso names
15:27:45 <pwhalen> https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-37-20220417.0/compose/IoT/x86_64/iso/Fedora-IoT-ostree-x86_64-37-20220417.0.iso
15:27:56 <pwhalen> which is now 'fixed'
15:29:09 <coremodule> nice! it looks fixed to me!
15:29:12 <coremodule> pwhalen++
15:29:23 <pwhalen> there was a compose attempt on the 18th, it failed with some infra issue by the looks of it
15:30:20 <pwhalen> ApplianceError: Image status is FAILED: 'utf-8' codec can't decode byte 0xf7 in position 16881: invalid start byte
15:30:39 <pwhalen> Likely a one off, we'll see the next attempt
15:31:01 <coremodule> sure, that sounds good
15:31:51 <coremodule> #topic 5) ==== Open Floor ====
15:32:17 <coremodule> anything for open floor? I don't have anything myself
15:32:49 <pwhalen> The osbuild change for iot was approved by Fesco
15:32:54 <pwhalen> https://fedoraproject.org/wiki/Changes/IoTArtifactsWithOSBuild
15:33:22 <pwhalen> There is still some work needed before we can move it over
15:34:22 <coremodule> #info Fedora IoT to be built with osbuild - approved by fesco
15:34:29 <coremodule> #link https://fedoraproject.org/wiki/Changes/IoTArtifactsWithOSBuild
15:35:12 <coremodule> #link https://pagure.io/fesco/issue/2778
15:35:55 <coremodule> what else needs to happen?
15:37:17 <pwhalen> A couple of features need to land in Fedora so we can produce all our deliverables
15:39:08 <coremodule> got it. well cool, that will be a good change. make IoT the true upstream of RHEL edge
15:42:14 <coremodule> alright, if nothing else, I'll close out the meeting...
15:42:28 <pwhalen> nothing from me
15:42:42 <coremodule> thanks pwhalen and bcotton for coming
15:42:44 <coremodule> #endmeeting