Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
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
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.
Comment 6Zbigniew Jędrzejewski-Szmek
2021-02-13 14:40:38 UTC
*** Bug 1927148 has been marked as a duplicate of this bug. ***
Comment 7Michel Alexandre Salim
2021-02-16 19:16:24 UTC