15:01:02 <coremodule> #startmeeting Fedora IoT Working Group Meeting
15:01:02 <zodbot> Meeting started Wed Apr 13 15:01:02 2022 UTC.
15:01:02 <zodbot> This meeting is logged and archived in a public location.
15:01:02 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:01:02 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:02 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
15:01:03 <coremodule> #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule
15:01:03 <zodbot> Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson
15:01:03 <coremodule> #topic roll call
15:02:51 * pwhalen is here
15:03:00 * dustymabe is here
15:03:16 <bcotton> .hello2
15:03:17 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
15:03:58 <coremodule> hi everyone, let's get started
15:04:04 <coremodule> #topic 1) ==== Working Group process and admin  ====
15:04:05 <coremodule> #link https://docs.fedoraproject.org/en-US/iot/
15:04:13 <coremodule> Anything for admin/docs?
15:04:27 <bcotton> ooh ooh
15:04:36 <dustymabe> .hi
15:04:39 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dusty@dustymabe.com>
15:04:59 <bcotton> #info bcotton has prepared a split of WG and user docs
15:05:00 <bcotton> #link https://github.com/fedora-iot/iot-docs/tree/split_docs
15:05:22 <bcotton> there's nothing particularly controversial here, so I'm ready to move forward with it if no one objects
15:05:52 <coremodule> no objection here
15:06:08 <bcotton> the one open question I had was if we're still using https://pagure.io/fedora-iot/issues or if we want to direct folks to GitHub or somewhere else
15:06:08 * pwhalen has none
15:07:30 <pwhalen> Doesnt look active, I have no objections
15:09:19 <bcotton> yea,h the lack of activity is what made me think there's another place we should be pointing people
15:09:23 <bcotton> but maybe not
15:09:24 <pwhalen> pbrobinson is out this week, he might have a preference
15:09:42 <bcotton> but we can leave it for now and figure that out later, too
15:10:53 <coremodule> I like that idea, just to get pbrobinson's input
15:11:24 <bcotton> anyway, that's all from me. i'll merge the branch and start the process of updating the docs-fp-o repo
15:11:57 <coremodule> that sounds great. thanks bcotton
15:13:34 <coremodule> #topic 2) ==== Fedora 35 status ====
15:13:34 <coremodule> #info Fedora-IoT-35-20220112.0
15:13:34 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20220112.0&groupid=1&groupid=5
15:14:19 <coremodule> There was a systemd update pushed last week for F35:
15:14:20 <coremodule> https://bodhi.fedoraproject.org/updates/FEDORA-2022-423231bb82
15:14:35 <bytehackr> just checked that maximum issues are older then 1 year, :D
15:14:38 <coremodule> But I'm not sure it fixed the problem, it looks like it is causing another issue:
15:14:44 <coremodule> https://bugzilla.redhat.com/show_bug.cgi?id=2074083
15:14:51 <coremodule> I'll spend some time looking into it.
15:15:09 <coremodule> #info systemd update pushed last week to fix /etc/resolv.conf issue
15:15:17 <coremodule> #link https://bodhi.fedoraproject.org/updates/FEDORA-2022-423231bb82
15:15:30 <coremodule> #info looks like it introduced some other errors:
15:15:36 <coremodule> #link https://bugzilla.redhat.com/show_bug.cgi?id=2074083
15:15:53 <coremodule> That's all I have for F35
15:16:18 <pwhalen> the mess continues :/
15:16:56 <pwhalen> there was a compose attempt made on Fedora-IoT-35-20220411.0
15:16:57 <coremodule> soon, f35 will just be a memory...
15:16:59 <coremodule> hah.
15:17:58 <pwhalen> look the same - https://koji.fedoraproject.org/koji/taskinfo?taskID=85477917
15:18:21 <pwhalen> Not sure if that included the updated systemd
15:19:18 <coremodule> Hmmm.... more fun.
15:20:22 <pwhalen> looks like it did systemd-249.11-1.fc35.aarch64.rpm
15:21:38 * dustymabe has an agenda item if there is time
15:22:01 <coremodule> pwhalen, where are you looking to see that?
15:22:19 <coremodule> dustymabe, definitely, F35, F36, or F37 related?
15:22:58 <pwhalen> coremodule: the compose logs
15:23:58 <dustymabe> coremodule: I guess F37 :)
15:25:04 <pwhalen> coremodule: move on ?
15:25:08 <coremodule> yeah
15:25:10 <coremodule> #topic 3) ==== Fedora 36 status ====
15:25:10 <coremodule> #info Fedora-IoT-36-20220411.0
15:25:10 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-IoT-36-20220411.0&groupid=1&groupid=5
15:25:17 <coremodule> F36 is looking good to me.
15:25:39 <pwhalen> yep, looks good
15:25:48 <coremodule> #info F36 looks good this week.
15:25:55 <coremodule> #topic 4) ==== Fedora 37/Rawhide status ====
15:25:55 <coremodule> #info Fedora-IoT-37-20220406.0
15:25:55 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=37&build=Fedora-IoT-37-20220406.0&groupid=1&groupid=5
15:26:03 <coremodule> Alright, dustymabe, take it away!
15:26:30 <dustymabe> coremodule: suggestion: #topic default/fallback hostname in Fedora
15:27:08 <coremodule> Okay, let's quickly go over F37 before changing topic...
15:27:26 <coremodule> Tests look good, haven't had a compose in a couple days, but I'm wondering if that's partially because pbrobinson is out?
15:28:39 <coremodule> #info Tests look good, haven't had a compose in a couple days
15:28:39 <pwhalen> he did one on the 11th, thats pretty recent
15:28:55 <pwhalen> sorry, I missed the topic change
15:29:24 <coremodule> #chair dustymabe
15:29:24 <zodbot> Current chairs: bcotton coremodule dustymabe pbrobinson puiterwijk pwhalen tdawson
15:30:17 <coremodule> #topic default/fallback hostname in Fedora
15:30:27 <coremodule> Okay, *now* the floor is all yours dustymabe :)
15:30:33 <dustymabe> hi all!
15:30:54 <pwhalen> howdy dustymabe :)
15:32:04 <dustymabe> sorry my connection dropped
15:32:06 <dustymabe> back now
15:32:21 <dustymabe> so i'm here to discuss a pain point we had in FCOS a little while back
15:32:35 <dustymabe> Back in Fedora 33 the default hostname was changed from `localhost` to `fedora` on instances that didn't get the hostname set in any other way (i.e. it's the fallback if it's not set anywhere else). As far as I know this change came in in systemd and was never proposed as a change in Fedora itself.
15:32:50 <dustymabe> Here's the original enablement upstream https://github.com/systemd/systemd/pull/5175 and the BZ requesting the change in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1392925
15:32:57 <dustymabe> Unfortunately, this initiallly caused us in FCOS some pain because reverse DNS lookups for hostname stopped working. This was subsequently fixed I believe, but it still remains that a lot of third party software will check to see if an instances hostname is "unset" by checking the current hostname against the string "localhost".
15:33:27 <dustymabe> The question I have here today is, what do we think the fallback hostname should be for Server like instances?
15:35:23 <pwhalen> right, I recall the unexpected change. Good question, has coreos decided on a short list?
15:35:36 <dustymabe> pwhalen: "short list" being?
15:35:53 <pwhalen> short list of options being considered
15:36:19 <dustymabe> we have an open ticket to discuss future steps: https://github.com/coreos/fedora-coreos-tracker/issues/902
15:36:42 <dustymabe> right now mainly being to figure out what other working groups think. If we can find agreement we'll propose a change and discuss with FESCO
15:38:12 <coremodule> dustymabe, what do you think the fallback should be? back to 'localhost'?
15:38:23 <dustymabe> the option I'm pursuing is to get the groups to agree that we want `localhost` as our fallback hostname and somehow implement that at the distro level (maybe fedora-release subpackages or something)
15:39:03 <dustymabe> but open to other options.. basically what we're looking for is backwards compat with what third party software expects, which is `localhost`.
15:39:20 <pwhalen> yea, I tend to agree
15:39:43 <pwhalen> as it was
15:39:52 <coremodule> +1 to that
15:40:39 <tdawson> Beyond scripts ... all the documentation that would have to change and be updated if it isn't "localhost" ... +1 to go back to "localhost"
15:40:53 <dustymabe> what's the best way to proceed to get an official answer from the IoT group on collaaboration on this effort?
15:41:02 <dustymabe> open a ticket and have people voice suppot there?
15:41:44 <dustymabe> and if so, which repo is best for that?
15:42:22 <coremodule> dustymabe, that's probably the most official way, yeah. could you send the ticket and a brief proposal to the iot list too?
15:42:32 <coremodule> probably here is the best play to open an issue:
15:42:32 <coremodule> https://pagure.io/fedora-iot/issues
15:42:43 <pwhalen> heh
15:42:44 <coremodule> pwhalen, do that repo work for you?
15:42:47 <coremodule> ^
15:42:49 <coremodule> *does
15:43:08 <pwhalen> yea, that was the one bcotton mentioned earlier.
15:43:13 <dustymabe> perfect, will do
15:43:17 <dustymabe> thanks all!
15:43:17 <coremodule> yeah, the never used one
15:43:48 <pwhalen> thanks for doing that dustymabe
15:43:50 * dustymabe heads off to another meeting
15:43:54 <dustymabe> thank you pwhalen!
15:44:00 <coremodule> thanks dustymabe
15:44:06 <pwhalen> dustymabe++
15:44:06 <zodbot> pwhalen: Karma for dustymabe changed to 9 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:45:18 <coremodule> #topic 5) ==== Open Floor ====
15:45:25 * pwhalen has nothing
15:45:30 <coremodule> Cool.
15:45:39 <coremodule> Thanks for attending this weeks meeting
15:46:01 <coremodule> #endmeeting