14:00:12 <pwhalen> #startmeeting Fedora IoT Working Group Meeting
14:00:12 <zodbot> Meeting started Wed Oct 16 14:00:12 2019 UTC.
14:00:12 <zodbot> This meeting is logged and archived in a public location.
14:00:12 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:12 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:00:12 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
14:00:12 <pwhalen> #chair pwhalen pbrobinson bcotton tdawson puiterwijk
14:00:12 <zodbot> Current chairs: bcotton pbrobinson puiterwijk pwhalen tdawson
14:00:12 <pwhalen> #topic roll call
14:00:21 <pwhalen> Good morning folks, who's here today?
14:00:47 <puiterwijk> Hi
14:00:49 <puiterwijk> .hello2
14:00:50 <zodbot> puiterwijk: puiterwijk 'Patrick Uiterwijk' <puiterwijk@redhat.com>
14:01:23 <pwhalen> howdy puiterwijk
14:01:56 * pbrobinson is here now
14:02:03 * pwhalen gives it a few minutes for others to join
14:02:30 * tdawson is here.
14:04:16 <pwhalen> ok, we appear to have most of the usual suspects. Lets start
14:04:25 <pwhalen> #topic 1) ==== Working Group process and admin  ====
14:04:25 <pwhalen> #link https://docs.fedoraproject.org/en-US/iot/
14:04:35 <pwhalen> anything for admin?
14:05:31 <pwhalen> I dont have anything myself. pbrobinson?
14:05:33 <pbrobinson> I filed a ticket with council for Edition promotion
14:06:03 <pbrobinson> #info filed a ticket with council for Edition promotion
14:06:07 <pbrobinson> #link https://pagure.io/Fedora-Council/tickets/issue/277
14:06:16 <pbrobinson> the plan is to soft launch with F-31
14:07:06 <pbrobinson> #info the plan is to soft launch with F-31, then do a full launch later
14:07:14 <puiterwijk> It looks like this discussion is starting right now, at the council meeting
14:07:23 <puiterwijk> Oh, after the inserted topic
14:07:45 <pbrobinson> right
14:07:51 <pbrobinson> that's all I have for admin
14:08:13 <pbrobinson> once council approves it then fesco deals with it, basically it becomes blocker status in the f32 time frame
14:08:39 <pwhalen> excellent
14:09:09 <pwhalen> ok, moving on
14:09:11 <pwhalen> #topic 2) ==== Fedora 30 status ====
14:09:11 <pwhalen> #info New compose available for testing
14:09:11 <pwhalen> #link https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-30-20191011/compose/
14:09:33 <pwhalen> I see we have a relatively new compose for f30, anyone hitting any issues?
14:10:45 <tdawson> I haven't tried it yet, so nope from me
14:11:10 <pbrobinson> there was some issue with the prior one that was pulling in wrong content from the change of stable/devel etc
14:11:11 <pwhalen> basic testing the disk images looks OK, not tried to upgrade
14:11:27 <pbrobinson> but that looks all good to me now
14:13:07 <pwhalen> upgrades in progress now
14:13:12 <pwhalen> any other in f30 issues?
14:14:10 <pbrobinson> none I'm aware of
14:14:17 <pwhalen> #topic 3) ==== Fedora 31 status ====
14:14:17 <pwhalen> #info New compose available for testing
14:14:17 <pwhalen> #link https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-31-20191014/compose/
14:14:36 <pwhalen> #undo
14:14:36 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x7f93f085dad0>
14:15:03 <pwhalen> #link https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-31-20191014.0/compose/
14:15:49 <pwhalen> not seeing any issues here either on a basic test.
14:16:21 <pwhalen> We did identify some problems during the iot test day, mostly hardware issues on the rpi3 (bluetooth, serial)
14:16:50 <pwhalen> not sure if thats changed at all with this latest compose.
14:17:25 <pbrobinson> bluetooth is a known issue
14:17:28 <pwhalen> the other issue was setting the hostname is initial-setup.
14:17:29 <pbrobinson> I have it on my list
14:17:42 <pbrobinson> I need to clean install my iot rpi to test the serial issues
14:19:19 <pbrobinson> any other issues from the test day?
14:19:23 <pwhalen> i tried both ttyS0, ttyS1 with the test day disk image, I'll try the latest
14:19:47 <pwhalen> #link http://testdays.fedorainfracloud.org/events/73
14:20:13 <pwhalen> tdawson, hit memory issues with the rpi3a
14:20:42 <tdawson> Well, those were the same issues as last test day, when building a container.
14:20:57 <pwhalen> #info configured host name not used on login (BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1757960 )
14:21:37 <pwhalen> the podman warnings are not specific to iot, and reported already
14:22:01 <pwhalen> think thats about it. Anyone else see something I missed?
14:24:13 <pwhalen> #topic 4) ==== Fedora 32 status ====
14:25:00 <pbrobinson> we've had some issues with compose, I think I've fixed at least one of those
14:25:08 <pbrobinson> but I've not had time to look properly
14:25:41 <pbrobinson> once main rawhide next completes I'll kick off another compose to see if that was the key problem
14:25:51 <pbrobinson> if anyone has time to dig further
14:26:41 <pwhalen> not seeing the issue on a quick glance, but will look a little more after the meeting
14:27:16 <pwhalen> anything else for f32?
14:27:28 <tdawson> How is the initial login with the F32 images?  Meaning ... how are we initially creating our users?
14:27:52 <pbrobinson> we have ignition in place and we should have the login side of things in place soon
14:28:03 <tdawson> OK
14:28:44 <pwhalen> right now I think its easiest to either rebase from f31 or copy your ssh key to root
14:30:08 <pwhalen> #topic 5) ==== Open Floor ====
14:30:19 <pwhalen> that's all I had. Anything for open floor?
14:30:25 <tdawson> Nothing from me
14:33:25 <pwhalen> Helps if I look at the right compose logs :D .. f32 compose failed on the aarch64 disk image
14:34:08 <pbrobinson> nothing from me
14:34:15 <pwhalen> #endmeeting