Description of problem: systemd-oomd is failing in openqa testing during startup fedora-Rawhide-Workstation-live-iso-x86_64-BuildFedora-Rawhide-20210208.n.0-base_services_start@64bit Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Boot the Workstation Live image from 20210208 https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210208.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-Rawhide-20210208.n.0.iso 2. 3. Actual results: [ 14.000576] fedora systemd[562]: systemd-oomd.service: Failed to determine user credentials: No such process [ 14.001522] fedora systemd[562]: systemd-oomd.service: Failed at step USER spawning /usr/lib/systemd/systemd-oomd: No such process [ 14.015743] fedora systemd[1]: systemd-oomd.service: Main process exited, code=exited, status=217/USER [ 14.016012] fedora systemd[1]: systemd-oomd.service: Failed with result 'exit-code'. [ 14.017820] fedora systemd[1]: Failed to start Userspace Out-Of-Memory (OOM) Killer. Expected results: It should startup Additional info: https://openqa.fedoraproject.org/tests/772018
Created attachment 1755771 [details] journal from the openqa instance logs, journalctl -o short-monotonic
glibc-2.32.9000-29.fc34.x86_64 systemd-247.3-1.fc34.x86_64 More package versions for this compose at: https://kojipkgs.fedoraproject.org//work/tasks/7773/61577773/anaconda-packaging.log
I put up https://src.fedoraproject.org/rpms/systemd/pull-request/49 to fix this. I haven't tested it out with a fresh install but the systemd-oom user appears to be missing from the image.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This should be a Final blocker, per "All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present" - https://fedoraproject.org/wiki/Fedora_34_Final_Release_Criteria#System_services . It also happens on KDE live installs, for the record.
*** Bug 1927148 has been marked as a duplicate of this bug. ***
Fixed in 247.3-2 built for Rawhide and F34