Uploaded image for project: 'CoreOS OCP'
  1. CoreOS OCP
  2. COS-2987

[coreos/fedora-coreos-tracker] selinux-policy-41.21-1.fc42: systemd-homed service fails to start

XMLWordPrintable

    • Upstream
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Integration & Delivery - 261
    • 0
    • 0.000

      [2605718916] Upstream Reporter: Aashish Radhakrishnan
      Upstream issue status: Closed
      Upstream description:

          1. Describe the bug

      In the recent rawhide tests, the kola tests seem to fail as the `systemd-homed `service 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](https://github.com/user-attachments/files/17478318/console.txt)
      [journal.txt](https://github.com/user-attachments/files/17478319/journal.txt)

          1. 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)

          1. Expected behavior

      kola tests to PASS

          1. 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
      ```

          1. System details

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

          1. Butane or Ignition config

      No response

          1. Additional information

      No response

              aaradhak@redhat.com Aashish Radhakrishnan
              upstream-sync Upstream Sync
              Adam Piasecki
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: