coreos / fedora-coreos-tracker

Issue tracker for Fedora CoreOS
https://fedoraproject.org/coreos/
264 stars 59 forks source link

selinux-policy-41.21-1.fc42: systemd-homed service fails to start #1817

Closed aaradhak closed 1 month ago

aaradhak commented 1 month ago

Describe the bug

In the recent rawhide tests, the kola tests seem to fail as the systemd-homedservice fails to start with selinux-policy-41.21-1.fc42 rpm.

=== RUN   ext.config.systemd.network-online
--- FAIL: ext.config.systemd.network-online (24.33s)
        harness.go:1823: mach.Start() failed: machine "66962155-444c-45b0-8711-8e732c9f2532" failed basic checks: detected failed or stuck systemd units: some systemd units failed: systemd-homed.service; <nil>
FAIL, output in tmp/kola/qemu-2024-10-22-1451-29
Error: harness: test suite failed
2024-10-22T14:51:26Z cli: harness: test suite failed

Console log:

         Starting systemd-homed.service - Home Area Manager...

[FAILED] Failed to start systemd-homed.service - Home Area Manager.

Journal log:

Oct 22 12:56:24.755219 systemd-homed.service[1847]: systemd-homed.service: Failed to set up special execution directory in /var/cache: Permission denied
Oct 22 12:56:24.755493 systemd-homed.service[1847]: systemd-homed.service: Failed at step CACHE_DIRECTORY spawning /usr/lib/systemd/systemd-homed: Permission denied
Oct 22 12:56:24.757977 init.scope[1]: systemd-homed.service: Main process exited, code=exited, status=239/CACHE_DIRECTORY
Oct 22 12:56:24.758121 init.scope[1]: systemd-homed.service: Failed with result 'exit-code'.
Oct 22 12:56:24.758992 init.scope[1]: Failed to start systemd-homed.service - Home Area Manager.
Oct 22 12:56:24.760000 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-homed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Ref: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8707c24571#comment-3771069 console.txt journal.txt

Reproduction steps

1) checkout rawhide repository 2) cosa fetch && cosa build 3) kola run ext.config.systemd.network-online (there are multiple kola test failures)

Expected behavior

kola tests to PASS

Actual behavior

=== RUN   ext.config.systemd.network-online
--- FAIL: ext.config.systemd.network-online (24.33s)
        harness.go:1823: mach.Start() failed: machine "66962155-444c-45b0-8711-8e732c9f2532" failed basic checks: detected failed or stuck systemd units: some systemd units failed: systemd-homed.service; <nil>
FAIL, output in tmp/kola/qemu-2024-10-22-1451-29
Error: harness: test suite failed
2024-10-22T14:51:26Z cli: harness: test suite failed

System details

fedora rawhide build - all platforms(x86_64, aarch64,ppc64le, s390x)

Butane or Ignition config

No response

Additional information

No response

aaradhak commented 1 month ago

Fast-track PR : https://github.com/coreos/fedora-coreos-config/pull/3220

dustymabe commented 1 month ago

The fix is now in rawhide and the fast-track was dropped in https://github.com/coreos/fedora-coreos-config/pull/3221