Fedora CoreOS Meeting Minutes 2022-03-09
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:16 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:22)
* Action items from last meeting (dustymabe, 16:35:07)
* the msi-x commit was reverted temporarily (again) in the Fedora
kernel while AWS works to upgrade instances so they will no longer
be affected
https://github.com/coreos/fedora-coreos-tracker/issues/1066#issuecomment-...
(dustymabe, 16:39:51)
* ACTION: ravanelli to look into the F36 changes 127 to see if this
change affects us on ppc64le (dustymabe, 16:41:33)
* CVE-2022-0847 (The Dirty Pipe Vulnerability) (dustymabe, 16:42:27)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1118
(dustymabe, 16:42:32)
* there is a `testing` and `next` stream release going out today with
the 5.16.13 kernel that should address the CVE (dustymabe,
16:43:12)
* Update the VMware metadata to new, modern defaults (dustymabe,
16:45:05)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1119
(dustymabe, 16:45:10)
* AGREED: We aren't opposed to updating the OVA to contain more modern
defaults, but would like to know how users can revert the behavior
if they need to since the platforms aren't EOL yet. We'd either need
some documentation to let the users know how or to know that the
users can ignore warnings and still proceed. (dustymabe, 17:03:43)
* open floor (dustymabe, 17:04:36)
* Here is the action update #127. The gcc ppc64le team was able build
fcos using F36 as host in a P9, P8 failed completely in the boot
part for F36, they are looking at it, looks the issue is related to
the bits change. I will keep an eye on how it is going (dustymabe,
17:04:58)
* Your time may shift in your locale in the coming weeks, but FCOS
community meetings will stay at 16:30 UTC. (dustymabe, 17:12:48)
Meeting ended at 17:15:44 UTC.
Action Items
------------
* ravanelli to look into the F36 changes 127 to see if this change
affects us on ppc64le
Action Items, by person
-----------------------
* ravanelli
* ravanelli to look into the F36 changes 127 to see if this change
affects us on ppc64le
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (71)
* miabbott (28)
* zodbot (26)
* jlebon (10)
* fifofonix (8)
* davdunc (6)
* travier (5)
* ravanelli (4)
* davdunc[m (3)
* jforbes (2)
* aaradhak (1)
* skunkerk (1)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
2 years, 1 month
D-Bus daemon don't work after ostree deployments.
by Yun Levi
Hello, all.
I'm trying to install my custom package and mange via ostree.
For this, I try to create some kernel modules and make a branch like below
mkdir -p /usr/lib/modules/5.15.18-200.fc35.x86_64/kernel/fs/
cp mymod.ko /usr/lib/modules/5.15.18-200.fc35.x86_64/kernel/fs/
ostree commit --base={comomit hash via rpm-ostree status -v} --branch=test/pkg/mymod .
// Get new commit hash
ostree admin deploy --staged --kargs=systemd.debug-shell {new commit hash}
Command is success and kernel booting has no problem.
But while systemd starting D-Bus service, It prints below errors.
2026 Mar 03 01:16:15 localhost systemd[1]: Started D-Bus System Message Bus.
2027 Mar 03 01:16:15 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/ systemd" hostname=? addr=? terminal=? res=success'
2028 Mar 03 01:16:15 localhost dbus-broker-launch[879]: ERROR launcher_run_child @ ../src/launch/launcher.c +325: Permission denied
2029 Mar 03 01:16:15 localhost dbus-broker-launch[867]: ERROR service_add @ ../src/launch/service.c +921: Transport endpoint is not connected
2030 Mar 03 01:16:15 localhost dbus-broker-launch[867]: launcher_add_services @ ../src/launch/launcher.c +804
2031 Mar 03 01:16:15 localhost dbus-broker-launch[867]: launcher_run @ ../src/launch/launcher.c +1409
2032 Mar 03 01:16:15 localhost dbus-broker-launch[867]: run @ ../src/launch/main.c +152
2033 Mar 03 01:16:15 localhost dbus-broker-launch[867]: main @ ../src/launch/main.c +178
2034 Mar 03 01:16:15 localhost dbus-broker-launch[867]: Exiting due to fatal error: -107
2035 Mar 03 01:16:15 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/s ystemd" hostname=? addr=? terminal=? res=failed'
2036 Mar 03 01:16:15 localhost systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
2037 Mar 03 01:16:15 localhost systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
I don't know why
../src/launch/launcher.c +325: Permission denied
happens, because /etc/machine-id has the same id to base image and permission has 0444 which means there should be no error on open.
(That code happen in sd_id128_get_machine function).
Am I missing somethings?
Thx.
2 years, 1 month
Fedora CoreOS Meeting Minutes 2022-03-02
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-02/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-02/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-02/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:19 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-02/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:23)
* Action items from last meeting (dustymabe, 16:34:21)
* ACTION: ravanelli to look into the F36 changes 127 to see if this
change affects us on ppc64le (dustymabe, 16:34:51)
* AWS m4.large instances fail to boot starting with 35.20211226.20.0
(dustymabe, 16:35:08)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1066
(dustymabe, 16:35:12)
* ACTION: davdunc to see if we can get the revert applied to the
latest fedora kernels again (dustymabe, 16:41:29)
* tracker: Fedora 36 changes considerations (dustymabe, 16:47:03)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/918
(dustymabe, 16:47:07)
* LINK: https://github.com/coreos/rpm-ostree/issues/3465 (dustymabe,
16:47:49)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1098
(dustymabe, 16:49:57)
* for 128 "GNU Toolchain Update (gcc 12, glibc 2.35)" the wiki says it
should be a backwards compatible change. We'll monitor, but for now
there is nothing for us to do. (dustymabe, 16:54:29)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1099
(dustymabe, 16:54:43)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1106
(dustymabe, 16:56:21)
* Consider releasing FCOS with a predictable release cadence
(dustymabe, 16:58:43)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1062
(dustymabe, 16:58:51)
* AGREED: We try to release every two weeks and we try to have
releases go out on Tuesday. We don't want to write down any more
contraints for ourselves than that so we don't waste time with the
details and focus on other work. (dustymabe, 17:14:02)
* open floor (dustymabe, 17:14:33)
* LINK: https://github.com/openshift/okd-machine-os/issues/210
(jlebon, 17:24:21)
* LINK: https://github.com/coreos/ignition/pull/1324 (dustymabe,
17:28:29)
Meeting ended at 17:29:52 UTC.
Action Items
------------
* ravanelli to look into the F36 changes 127 to see if this change
affects us on ppc64le
* davdunc to see if we can get the revert applied to the latest fedora
kernels again
Action Items, by person
-----------------------
* davdunc
* davdunc to see if we can get the revert applied to the latest fedora
kernels again
* **UNASSIGNED**
* ravanelli to look into the F36 changes 127 to see if this change
affects us on ppc64le
People Present (lines said)
---------------------------
* dustymabe (111)
* travier (56)
* zodbot (21)
* nemric (18)
* davdunc (16)
* jlebon (15)
* lucab (4)
* walters (4)
* fifofonix (2)
* miabbott (2)
* lucab_ (2)
* jbrooks (1)
* aaradhak[m] (1)
* aaradhak (1)
* skunkerk (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
2 years, 1 month