April 2022 - CoreOS - Fedora mailing-lists

Fedora CoreOS Meeting Minutes 2022-04-27
by Dusty Mabe 28 Apr '22

28 Apr '22

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos… Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos… ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by dustymabe at 16:30:24 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos… . Meeting summary --------------- * roll call (dustymabe, 16:30:29) * Action items from last meeting (dustymabe, 16:36:24) * jlebon reached out and we have reps from the nmstate here with us today (dustymabe, 16:36:45) * jaimelm and dustymabe met with Fedora releng/infra to discuss forward strategy for Fedora container hosting. The goal is to get off of their own infra and onto quay.io (https://pagure.io/fedora-infrastructure/issue/10386) thought they have some open questions about if flatpaks can be hosted there. (dustymabe, 16:37:21) * We are going to all work together over the next week to try to chase down any open questions and then move forward with putting our FCOS containers in quay.io if no blockers are found. (dustymabe, 16:37:38) * This will lead Fedora's transition to quay.io by some months, but the releng/infra team feels it's best if we start there for new containers rather than go to the old infra right before a transition. (dustymabe, 16:37:49) * New Package Request: nmstate-libs and nmstate (dustymabe, 16:39:58) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1175 (dustymabe, 16:40:03) * AGREED: nmstate is useful for dynamically configuring a running system OR generating NM keyfiles with no running system needed. The nmstate YAML config itself can't be used on system boot without an accompanying service to apply the config. In order to use it for provisioning a user would need to write a systemd unit themselves to apply the config they wrote using Ignition. At this time (dustymabe, 17:33:05) * open floor (dustymabe, 17:35:58) * LINK: https://discussion.fedoraproject.org/t/automated-fedora-coreos-35-for-raspb… (aaradhak[m], 17:36:34) * we will be having our FCOS community video meeting next Wednesday at https://meet.google.com/meo-enbb-rur?hs=224 (dustymabe, 17:39:18) Meeting ended at 17:41:03 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (87) * zodbot (27) * ffmancera (26) * jlebon (25) * walters (22) * thaller (18) * lucab (11) * aaradhak[m] (4) * miabbott (2) * jbrooks (1) * gursewak (1) * saqali (1) * aaradhak (1) * jaimelm (1) * ravanelli (1) * mnguyen (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

[Fedocal] Reminder meeting : Fedora CoreOS Group Weekly Meeting
by dusty＠dustymabe.com 26 Apr '22

26 Apr '22

Dear all, You are kindly invited to the meeting: Fedora CoreOS Group Weekly Meeting on 2022-04-27 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.libera.chat The meeting will be about: This is the meeting for the Fedora CoreOS Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://github.com/coreos/fedora-coreos-tracker/labels/meeting. For how to run the meeting, see https://github.com/coreos/fedora-coreos-tracker#steps-to-run-the-meeting Source: https://calendar.fedoraproject.org//meeting/9437/

1 0

Fedora CoreOS Meeting Minutes 2022-04-20
by Timothée Ravier 21 Apr '22

21 Apr '22

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-20/fedora_coreos… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-20/fedora_coreos… Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-20/fedora_coreos… ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by travier at 16:29:24 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-20/fedora_coreos… . Meeting summary --------------- * roll call (travier, 16:29:30) * Action items from last meeting (jlebon, 16:35:25) * tracker: Fedora 36 changes considerations (jlebon, 16:36:12) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/918 (jlebon, 16:36:20) * New Package Request: nmstate-libs and nmstate (jlebon, 16:38:53) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1175 (jlebon, 16:38:56) * ACTION: jlebon to reach out to nmstate team to make sure they can attend a future meeting to discuss this ticket (jlebon, 16:49:09) * develop strategy around organization and naming for our containers in quay.io (jlebon, 16:49:24) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1171 (jlebon, 16:49:27) * AGREED: We have decided that we'll punt on long term strategy for coreos-assembler container location. We'll reach out to Fedora infra/releng to investigate long term strategy for what registry Fedora containers will be hosted in. For the kubevirt and ostree containers we'll host them wherever Fedora officially hosts its containers and name them `fedora-coreos-kubevirt` and (dustymabe, 17:17:08) * Open Floor (jlebon, 17:18:55) * ACTION: jaimelm and dustymabe to meet with the releng/infra team to talk about containers and where everything fits (dustymabe, 17:24:08) Meeting ended at 17:30:33 UTC. Action Items ------------ * jlebon to reach out to nmstate team to make sure they can attend a future meeting to discuss this ticket * jaimelm and dustymabe to meet with the releng/infra team to talk about containers and where everything fits Action Items, by person ----------------------- * dustymabe * jaimelm and dustymabe to meet with the releng/infra team to talk about containers and where everything fits * jaimelm * jaimelm and dustymabe to meet with the releng/infra team to talk about containers and where everything fits * jlebon * jlebon to reach out to nmstate team to make sure they can attend a future meeting to discuss this ticket * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (86) * jlebon (65) * zodbot (22) * bgilbert (20) * travier (18) * jaimelm (10) * walters (3) * gursewak (2) * aaradhak[m] (2) * jbrooks (1) * jaimelm_ (1) * lorbus (1) * saqali (1) * davdunc (1) * aaradhak (1) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

[Fedocal] Reminder meeting : Fedora CoreOS Group Weekly Meeting
by dusty＠dustymabe.com 19 Apr '22

19 Apr '22

Dear all, You are kindly invited to the meeting: Fedora CoreOS Group Weekly Meeting on 2022-04-20 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.libera.chat The meeting will be about: This is the meeting for the Fedora CoreOS Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://github.com/coreos/fedora-coreos-tracker/labels/meeting. For how to run the meeting, see https://github.com/coreos/fedora-coreos-tracker#steps-to-run-the-meeting Source: https://calendar.fedoraproject.org//meeting/9437/

1 0

Fedora CoreOS Meeting Minutes 2022-04-13
by Jonathan Lebon 13 Apr '22

13 Apr '22

Minutes: https://meetbot-raw.fedoraproject.org/teams/fedora_coreos_meeting/fedora_co… Minutes (text): https://meetbot-raw.fedoraproject.org/teams/fedora_coreos_meeting/fedora_co… Log: https://meetbot-raw.fedoraproject.org/teams/fedora_coreos_meeting/fedora_co… ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by jlebon at 16:31:11 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-13/fedora_coreos… . Meeting summary --------------- * roll call (jlebon, 16:31:17) * Action items from last meeting (jlebon, 16:35:21) * F36: Fedora CoreOS Test Week (jlebon, 16:35:57) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1123 (jlebon, 16:35:59) * F36: No network on rpi4 (dustymabe, 16:37:07) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1145 (dustymabe, 16:37:13) * rebasing to another stream fails when deployment is staged (dustymabe, 16:37:19) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1150 (dustymabe, 16:37:23) * F36: 36.20220325.1.0 NetworkManager not allowed to access NM dispatcher scripts (dustymabe, 16:37:29) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1156 (dustymabe, 16:37:34) * F36 VM fails to display the network device information on console (dustymabe, 16:37:40) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1153 (dustymabe, 16:37:44) * exoscale: disk images fail to provision (dustymabe, 16:37:49) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1160 (dustymabe, 16:37:55) * Fedora36 Next Auto-Upgrade Fails & Yields Grub Prompt (dustymabe, 16:38:12) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1149 (dustymabe, 16:38:17) * LINK: https://github.com/coreos/fedora-coreos-docs/pulls?q=is%3Apr+ (dustymabe, 16:40:10) * rebasing to another stream fails when deployment is staged (jlebon, 16:45:15) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1150 (jlebon, 16:45:21) * LINK: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9c21ee528d (jlebon, 16:48:37) * this UX issue should be fixed by ostree 2022.2 (https://github.com/ostreedev/ostree/pull/2524) (jlebon, 16:53:05) * Fedora CoreOS talks for devconf.us 2022 (jlebon, 16:53:28) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1154 (jlebon, 16:53:30) * tracker: Fedora 36 changes considerations (jlebon, 16:55:39) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/918 (jlebon, 16:55:45) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1098 (dustymabe, 16:59:19) * LINK: https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html (dustymabe, 17:02:53) * we are now in final freeze. we will be doing next releases weekly. (jlebon, 17:04:23) * Open Floor (jlebon, 17:05:08) * LINK: https://github.com/coreos/vagrant-ignition/ (bgilbert, 17:08:16) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/144 (bgilbert, 17:13:23) Meeting ended at 17:16:18 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (67) * jlebon (56) * zodbot (20) * bgilbert (16) * travier (5) * davdunc (5) * mnguyen_ (3) * saqali (1) * aaradhak (1) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

Networking not coming up during boot
by Beat Kuster 13 Apr '22

13 Apr '22

Dear Fedora CoreOS Community I did have FCOS installed on multiple Intel NUCs for a long time and was always very happy. Being on board since CentOS Atomic Host, Fedora CoreOS really is an outstandig product, thank you so much for making this possible. Now to the issue: My current system (NUC8i5BEK) has a Zincati maintenance window defined and after updates reboots automatically during this time window. Unfortunately, since release 35.20220116.3.0, it seems that networking does not come up reliably after a reboot. The boot process gets stuck and the system does not request an IP from the DHCP. (Somehow sounded a bit like https://github.com/coreos/fedora-coreos-tracker/issues/1066 but my network driver "e1000e" is different) I identified two workarounds: - physically access the system and select at boot loader menu the last working release (~rollback) - reboot multiple times, sometimes networking magically comes up Last working release: 35.20220103.3.0 -> please note that this release always boots the first time even as of today Not working releases: 35.20220116.3.0, 35.20220131.3.0, 35.20220213.3.0 Could you please share any guidance how I could proceed? Provide more technical details here in the mailing list? Or opening a bug at https://github.com/coreos/fedora-coreos-tracker? Thanks in advance for any feedback, Beat

2 6

[Fedocal] Reminder meeting : Fedora CoreOS Group Weekly Meeting
by dusty＠dustymabe.com 12 Apr '22

12 Apr '22

Dear all, You are kindly invited to the meeting: Fedora CoreOS Group Weekly Meeting on 2022-04-13 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.libera.chat The meeting will be about: This is the meeting for the Fedora CoreOS Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://github.com/coreos/fedora-coreos-tracker/labels/meeting. For how to run the meeting, see https://github.com/coreos/fedora-coreos-tracker#steps-to-run-the-meeting Source: https://calendar.fedoraproject.org//meeting/9437/

1 0

Bare metal with wifi network installation
by Aleksandar Kostadinov 12 Apr '22

12 Apr '22

Hi, I decided to try CoreOS for my home bastion server as a cool way to keep configuration in one place and reproducibly be able to provision this and other machines in the future. I see troubles how should I layer RPMs though. The way I see in docs [1] is to create a service. But then I want to install: * NetworkManager-... * ddclient The issue is apparently bigger with NetworkManager because the packages need to be there before there is a network to install packages. My question is whether it is possible to layer additional packages with butane/ignition at installation time so that I don't need a package installation service and I can have a wifi network operational after install? I see that in the installation media the network manager modules are missing to establish a wifi connection. It is fine to do initial provisioning over cable. But I want to install the thing, bring it at it's desired destination, power it and expect it to work. btw bonus task is not to store wifi password inside initrd. Also I have another password for ddclient in butane. Can this also be protected? By protected I mean to be on the LUKS encrypted root that butane seems to support. Thank you! [1] https://docs.fedoraproject.org/en-US/fedora-coreos/os-extensions/

2 1

Re: [Now Playing] Fedora 36 Test Days
by Luna Jernberg 10 Apr '22

10 Apr '22

And next week is CoreOS Test Days, F36 Audio and Updates Test Days Will miss the next Update and Audio test days however, as i am gonna attend a demoparty event with some friends: https://2022.revision-party.net/ with some friends, but did my last Kernel testing today and will do my last CoreOS testing tommorow On 4/8/22, Luna Jernberg <droidbittin(a)gmail.com> wrote: > Hey! > > Helping out here and there when i can over the week :) > > On Fri, Apr 8, 2022 at 12:10 PM Sumantro Mukherjee <sumukher(a)redhat.com> > wrote: > >> Hey Fedorans, >> >> As most of you might know, we have Fedora testing events happening where >> you all >> can participate. As of today, we are running 3 events in parallel. >> >> 1. Kernel 5.17 Test Week [0] >> 2. Fedora 36 CoreOS [1] >> 3. Fedora Cloud Test Day [2] >> >> These are events that are easy to start off if you are new to Fedora >> and some of them >> even reward you with a Fedora Badge as token of gratitude and reward >> for your time and energy >> that you spent contributing! >> >> The wikis below will guide you through the instructions and how to >> participate. In case of an >> unlikely event of things not working as intended. File a bug and if >> you have any questions, >> reach out to @test list directly. >> >> In the coming week, we have two of the most community impacting topics >> that we will test for >> the Audio and Upgrade path to Fedora 36 from Fedora 35 and Fedora 34. >> More details can you found >> in this Fedora Magazine Article[3] >> >> [0] >> http://fedoraproject.org/wiki/Test_Day:2022-04-03_Kernel_5.17_Test_Week >> [1] http://fedoraproject.org/wiki/Test_Day:Fedora_36_CoreOS_2022-04-04 >> [2] >> http://fedoraproject.org/wiki/Test_Day:2022-04-08_Fedora_36_Cloud_Testday >> [3] >> https://fedoramagazine.org/contribute-at-the-fedora-kernel-5-17-coreos-clou… >> >> >> -- >> //sumantro >> Fedora QE >> TRIED AND PERSONALLY TESTED, ERGO TRUSTED >> _______________________________________________ >> test mailing list -- test(a)lists.fedoraproject.org >> To unsubscribe send an email to test-leave(a)lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure >> >

1 0

Fwd: [Now Playing] Fedora 36 Test Days
by Luna Jernberg 08 Apr '22

08 Apr '22

---------- Forwarded message --------- From: Luna Jernberg <droidbittin(a)gmail.com> Date: Fri, Apr 8, 2022 at 12:26 PM Subject: Re: [Now Playing] Fedora 36 Test Days To: For testing and quality assurance of Fedora releases < test(a)lists.fedoraproject.org>, <coreos(a)lists.fedoraproject.org>, < cloud(a)lists.fedoraproject.org>, Sumantro Mukherjee <sumukher(a)redhat.com>, Luna Jernberg <bittin(a)fedoraproject.org>, Martin Jernberg < droidbittin(a)gmail.com> Cc: <test-announce(a)lists.fedoraproject.org>, Community support for Fedora users <users(a)lists.fedoraproject.org>, <kernel(a)lists.fedoraproject.org> Hey! Helping out here and there when i can over the week :) On Fri, Apr 8, 2022 at 12:10 PM Sumantro Mukherjee <sumukher(a)redhat.com> wrote: > Hey Fedorans, > > As most of you might know, we have Fedora testing events happening where > you all > can participate. As of today, we are running 3 events in parallel. > > 1. Kernel 5.17 Test Week [0] > 2. Fedora 36 CoreOS [1] > 3. Fedora Cloud Test Day [2] > > These are events that are easy to start off if you are new to Fedora > and some of them > even reward you with a Fedora Badge as token of gratitude and reward > for your time and energy > that you spent contributing! > > The wikis below will guide you through the instructions and how to > participate. In case of an > unlikely event of things not working as intended. File a bug and if > you have any questions, > reach out to @test list directly. > > In the coming week, we have two of the most community impacting topics > that we will test for > the Audio and Upgrade path to Fedora 36 from Fedora 35 and Fedora 34. > More details can you found > in this Fedora Magazine Article[3] > > [0] > http://fedoraproject.org/wiki/Test_Day:2022-04-03_Kernel_5.17_Test_Week > [1] http://fedoraproject.org/wiki/Test_Day:Fedora_36_CoreOS_2022-04-04 > [2] > http://fedoraproject.org/wiki/Test_Day:2022-04-08_Fedora_36_Cloud_Testday > [3] > https://fedoramagazine.org/contribute-at-the-fedora-kernel-5-17-coreos-clou… > > > -- > //sumantro > Fedora QE > TRIED AND PERSONALLY TESTED, ERGO TRUSTED > _______________________________________________ > test mailing list -- test(a)lists.fedoraproject.org > To unsubscribe send an email to test-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure >

1 0

2024

2023

2022

2021

2020

2019

2018

CoreOS April 2022