June 2020 - CoreOS - Fedora mailing-lists

[Fedocal] Reminder meeting : Fedora CoreOS Group Weekly Meeting
by dusty＠dustymabe.com 30 Jun '20

30 Jun '20

Dear all, You are kindly invited to the meeting: Fedora CoreOS Group Weekly Meeting on 2020-07-01 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net 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://apps.fedoraproject.org/calendar/meeting/9437/

1 0

Change to network interface naming on new installs
by Luca BRUNO 25 Jun '20

25 Jun '20

TLDR: Due to a bug, all current FCOS machines are using legacy network interface naming (e.g. `eth0`). Fixing and changing the default naming scheme will be targeted at freshly provisioned instances *ONLY*. Existing instances will be able to switch to the new scheme via manual intervention. Hi all, Due to an oversight, network interfaces (NICs) on Fedora CoreOS are currently named using the kernel's default scheme (e.g. `eth0`). Depending on the order that devices are discovered, these names can change from boot to boot. Unfortunately we did not realize this until recently, as described in #484[0]. This means that currently all FCOS nodes on all streams (thus including `stable`) are not using predictable interface names[1] as used in other Fedora Editions and Linux distributions. Starting with the next release cycle we plan to fix this bug, thus changing the default behavior for new Fedora CoreOS releases. As this is a quite invasive behavioral change, it will only affect newly-provisioned machines. NIC names on existing systems will not change, as upgrades there will automatically pin the current behavior via the kernel command line. The ticket above has further details on the plan of action, but in short we are going to: * (in the upcoming release cycle) pin existing nodes into their current naming scheme[2] * (in the release cycle after that) switch to persistent naming scheme for new nodes[3] If everything goes as planned, the end result is that: * freshly provisioned instances will use the persistent naming scheme only * existing instances will stick to their existing naming scheme * in those cases where it is safe to change existing behavior, manual intervention can be applied to opt-in into the new default behavior If you deploy Fedora CoreOS using an Ignition config that references NICs by name, you'll need to update your config to reflect the new naming. Also, if you have a mixed fleet of older and newer Fedora CoreOS installs, note that NIC names may not be consistent across machines (unless manually switched). We will keep posting progress and updates to the bug tracker, please keep watching #484[0] for details. 0: https://github.com/coreos/fedora-coreos-tracker/issues/484 1: https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.… 2: https://github.com/coreos/fedora-coreos-config/pull/490 3: https://github.com/coreos/fedora-coreos-config/pull/491 Ciao, Luca

1 0

Fedora CoreOS Meeting Minutes 2020-06-24
by Dusty Mabe 24 Jun '20

24 Jun '20

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-24/fedora_coreos… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-24/fedora_coreos… Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-24/fedora_coreos… ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by bgilbert at 16:31:37 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-24/fedora_coreos… . Meeting summary --------------- * roll call (bgilbert, 16:31:44) * Action items from last meeting (dustymabe, 16:35:03) * LINK: https://github.com/rpm-software-management/rpm/issues/1273 (jlebon, 16:36:14) * upstream RFE for RPM supporting runtime LUA scriptlets https://github.com/rpm-software-management/rpm/issues/1273 (dustymabe, 16:36:43) * network interface name differs between Fedora CoreOS and RedHat CoreOS (dustymabe, 16:37:25) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/484 (dustymabe, 16:37:31) * AGREED: the tentative schedule is to release a barrier stable release next week to convert existing systems to using net.ifnames=0 via karg and then in the following stable release (july 14) deliver the change that will cause NIC naming to get corrected to the desired behavior (dustymabe, 17:05:35) * Release notes (dustymabe, 17:06:20) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/194 (dustymabe, 17:06:27) * open floor (dustymabe, 17:30:13) * LINK: https://github.com/coreos/ssh-key-dir/issues/10 (bgilbert, 17:32:34) Meeting ended at 17:36:26 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (112) * lucab (41) * bgilbert (35) * jlebon (34) * zodbot (20) * cyberpear (14) * lorbus (3) * davdunc (2) * darkmuggle (1) * Guest24063 (1) * jdoss (1) * cverna (1) * skunkerk (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

how to use wireguard on coreos?
by Farkas Levente 24 Jun '20

24 Jun '20

hi, what's the current concept about wireguard on coreos? as of now wireguard kernel module already included in fedora and the base kernel on fedora coreos. how can one use it? and may be not just this but other kernel module. - what's the situation with the container base os? eg can i use wireguard on coreos while the container based on ubuntu (since many or even most container us it as a base os)? - should i've to use the same fedora based base image and can't use any other containers? i'm not able to load the kernel module if i use different base image. - should i've to preload (modprobe) the kernel module on the host or should i leave it to wireguard-tools? - which kind of network mode should i use? - is it possible to use --net=host? for me it seems i can't. - can i use a container which create, setup and manage the vpn network while other container on the same host use it? or i've to add it to all containers? - can i somehow setup an overlay network with wireguard? -- Levente "Si vis pacem para bellum!"

1 0

Fedora CoreOS Meeting Minutes 2020-06-17
by Jonathan Lebon 18 Jun '20

18 Jun '20

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:30:32 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-17/fedora_coreos… . Meeting summary --------------- * roll call (jlebon, 16:30:42) * Action items from last meeting (jlebon, 16:33:14) * crypto-policies pinned to avoid Lua script (jlebon, 16:35:48) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/540 (jlebon, 16:35:58) * AGREED: we will work around the crypto-policies issue for now in rpm-ostree. meanwhile, we will also pursue a path forward with upstream rpm to support passing lua scriptlets at runtime (jlebon, 17:02:51) * F32 rebase tracker for changes discussion (jlebon, 17:03:07) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/372 (jlebon, 17:03:10) * LINK: https://github.com/coreos/fedora-coreos-config/pull/481#issuecomment-645038… (dustymabe, 17:06:12) * potential issues with microcode_ctl rolling out in testing/next (jlebon, 17:10:20) * LINK: https://github.com/coreos/fedora-coreos-config/pull/481#issuecomment-645038… (jlebon, 17:10:26) * LINK: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/… (dustymabe, 17:11:47) * Open Floor (jlebon, 17:22:11) * ACTION: jlebon to open an RFE in upstream RPM for supporting runtime Lua scriptlets (jlebon, 17:23:29) Meeting ended at 17:32:22 UTC. Action Items ------------ * jlebon to open an RFE in upstream RPM for supporting runtime Lua scriptlets Action Items, by person ----------------------- * jlebon * jlebon to open an RFE in upstream RPM for supporting runtime Lua scriptlets * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jlebon (91) * dustymabe (82) * bgilbert (19) * lucab (18) * zodbot (16) * cyberpear (14) * skunkerk (2) * darkmuggle (1) * ksinny (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

audit and selinux messages
by Farkas Levente 17 Jun '20

17 Jun '20

Hi, Has Anyone used to see the console of a coreos machine? bare metal or even virt? It's full of audit and selinux messages. simple it's impossible to read and write anything on it. Can you login on the console? Nobody really cares about it? -- Levente "Si vis pacem para bellum!"

3 4

Fedora CoreOS Meeting Minutes 2020-06-10
by Dusty Mabe 11 Jun '20

11 Jun '20

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-10/fedora_coreos… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-10/fedora_coreos… Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-10/fedora_coreos… ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by dustymabe at 16:30:03 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-10/fedora_coreos… . Meeting summary --------------- * roll call (dustymabe, 16:30:08) * Action items from last meeting (dustymabe, 16:32:53) * we had the FCOS test day and I did send out a coreos-status post with relevant information (dustymabe, 16:33:46) * meeting agenda items for today (dustymabe, 16:34:12) * FCOS test day on 06/08 (dustymabe, 16:36:52) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/491 (dustymabe, 16:36:57) * LINK: http://testdays.fedorainfracloud.org/events/84 (dustymabe, 16:37:34) * we need documentation for openstack deployments (dustymabe, 16:43:43) * we had a productive test day with a lot of feedback and a few cosmetic issues found, we're still processing the feedback (dustymabe, 16:44:15) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/422#issuecomment-607… (dustymabe, 16:46:03) * F32 rebase tracker for changes discussion (dustymabe, 16:49:22) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/372 (dustymabe, 16:49:29) * we build FCOS with the fedora modular repos as inputs, but we have those repos disabled by default on the running FCOS systems. We're proposing to just turn off the modular repos for the FCOS builds as well. Doing this will make package layering on top of f32 more reliable and also will hopefully make rebases to f32 less likely to fail. This is documented in (dustymabe, 16:53:12) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/525 (dustymabe, 16:53:13) * Need dnsmasq for podman to create CNI networks (dustymabe, 16:58:49) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/519 (dustymabe, 16:58:55) * F33 feature/change proposal SwapOnZRAM by default (dustymabe, 17:15:07) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/509 (dustymabe, 17:15:13) * open floor (dustymabe, 17:38:23) Meeting ended at 17:40:55 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (130) * lucab (24) * zodbot (23) * cmurf (19) * cyberpear (19) * jlebon (15) * jdoss (5) * lorbus (5) * adamw (4) * miabbott (2) * skunkerk (1) * slowrie (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : Fedora CoreOS Group Weekly Meeting
by dusty＠dustymabe.com 09 Jun '20

09 Jun '20

Dear all, You are kindly invited to the meeting: Fedora CoreOS Group Weekly Meeting on 2020-06-10 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net 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://apps.fedoraproject.org/calendar/meeting/9437/

1 0

Fedora CoreOS rebasing to Fedora 32: known issues; upcoming test day
by Dusty Mabe 03 Jun '20

03 Jun '20

1 0

Fedora CoreOS Meeting Minutes 2020-06-03
by Dusty Mabe 03 Jun '20

03 Jun '20

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-03/fedora_coreos… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-03/fedora_coreos… Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-03/fedora_coreos… ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by dustymabe at 16:30:52 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2020-06-03/fedora_coreos… . Meeting summary --------------- * roll call (dustymabe, 16:30:56) * Action items from last meeting (dustymabe, 16:33:50) * meeting agenda (dustymabe, 16:34:45) * LINK: https://github.com/coreos/fedora-coreos-tracker/labels/meeting (dustymabe, 16:35:31) * Fedora Test day for our `next` stream (Fedora 32) (dustymabe, 16:37:59) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/491 (dustymabe, 16:38:04) * LINK: https://fedoraproject.org/wiki/Test_Day:Fedora_32_CoreOS_2020-06-08 (kparal, 16:38:17) * we have just moved our `testing` stream over to Fedora 32 (dustymabe, 16:38:18) * LINK: http://testdays.fedorainfracloud.org/events/84 (kparal, 16:38:28) * ACTION: dustymabe and jlebon (and anyone else who wants to) will review test cases linked from the various test day pages and try to fixup things that need fixing (dustymabe, 16:45:33) * FCOS test day announcement on the qa fedora list: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/… (dustymabe, 16:51:10) * F32 rebase tracker for changes discussion (dustymabe, 16:51:48) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/372 (dustymabe, 16:51:52) * known issue in f32 testing release with selinux labeling absolute symlinks after ignition run https://github.com/coreos/fedora-coreos-tracker/issues/512 (dustymabe, 16:54:02) * known kernel issue in f32 testing when testing our nodes on AWS https://github.com/coreos/fedora-coreos-tracker/issues/507 (dustymabe, 16:55:14) * AGREED: we'll send out a coreos-status post with some relevant information about the rebase to f32 and possible issues people might be seeing (dustymabe, 16:58:37) * ACTION: dustymabe to send coreos-status post with relevant information about the change to fedora 32 (dustymabe, 17:01:24) * RFC: Merge coreos/ignition-dracut into coreos/ignition (dustymabe, 17:01:47) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/511 (dustymabe, 17:01:53) * AGREED: Merging ignition-dracut into ignition seems to have clear advantages and the disadvantages seem to be minor or easily worked around. We'll merge them together in the future (when it's safest to do so) unless clear blockers come up when attempting the transition. (dustymabe, 17:16:33) * network interface name differs between Fedora CoreOS and RedHat CoreOS (dustymabe, 17:17:53) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/484 (dustymabe, 17:18:00) * AGREED: For this issue we'd like to correct the behavior but realize it would be a disruption for existing nodes that upgrade. We propose to add a barrier node in our update graph that will keep behavior for updating nodes the same, while fixing the bug and causing new behavior for newly installed nodes. (dustymabe, 17:26:08) * open floor (dustymabe, 17:28:29) * LINK: https://bugzilla.redhat.com/userprefs.cgi?tab=component_watch (bcotton, 17:33:12) Meeting ended at 17:45:36 UTC. Action Items ------------ * dustymabe and jlebon (and anyone else who wants to) will review test cases linked from the various test day pages and try to fixup things that need fixing * dustymabe to send coreos-status post with relevant information about the change to fedora 32 Action Items, by person ----------------------- * dustymabe * dustymabe and jlebon (and anyone else who wants to) will review test cases linked from the various test day pages and try to fixup things that need fixing * dustymabe to send coreos-status post with relevant information about the change to fedora 32 * jlebon * dustymabe and jlebon (and anyone else who wants to) will review test cases linked from the various test day pages and try to fixup things that need fixing * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (131) * cyberpear (38) * jlebon (33) * kparal (32) * bgilbert (25) * zodbot (23) * lucab (19) * darkmuggle (13) * slowrie (13) * sumantro (9) * bcotton (8) * coremodule (3) * jdoss (1) * skunkerk (1) * davdunc (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2024

2023

2022

2021

2020

2019

2018

CoreOS June 2020