Bug 2013559

Summary: After upgrade Fedora 34 to systemd 247.8 the system fails to boot ~ 50% of the time
Product: [Fedora] Fedora Reporter: Kostya Vasilyev <kmansoft>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 34CC: fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, ssahani, s, systemd-maint, yuwatana, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-13 09:20:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Changes in the most recent dnf upgrade
none
journalctl -xb none

Description Kostya Vasilyev 2021-10-13 08:45:37 UTC
Created attachment 1832529 [details]
Changes in the most recent dnf upgrade

Description of problem:

Today dnf upgrade pulled in new systemd version, 247.8.

After this, about half the time the system fails to start, dumping me to the root recovery prompt. If I just press Ctrl+D the system boots to the display manager successfully.


Version-Release number of selected component (if applicable):

systemd 247.8

How reproducible:

Rebooted maybe 5-8 times, got the recovery prompt half of those times.


Steps to Reproduce:
1. Try to boot / reboot the system as usual

Actual results:

The text mode recovery prompt about half the time.


Expected results:

Normal boot to graphical display manager.

Additional info:

Attaching the results of journalctl -xb which shows a bunch of failed services due to rate limiting (?):

-----
Oct 13 11:32:45 fergie systemd[1]: ostree-remount.service: Failed with result 'start-limit-hit'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit ostree-remount.service has entered the 'failed' state with result 'start-limit-hit'.
Oct 13 11:32:45 fergie systemd[1]: Failed to start OSTree Remount OS/ Bind Mounts.
░░ Subject: A start job for unit ostree-remount.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit ostree-remount.service has finished with a failure.
░░ 
░░ The job identifier is 1284 and the job result is failed.
-----

Also attaching the output of "dns history info last" which contains information about the most recent upgrade, after which the issue started.

Comment 1 Kostya Vasilyev 2021-10-13 08:46:33 UTC
Created attachment 1832530 [details]
journalctl -xb

Comment 2 Kostya Vasilyev 2021-10-13 08:47:25 UTC
Sorry systemd 248.8 not 247.8

Comment 3 Zbigniew Jędrzejewski-Szmek 2021-10-13 09:20:39 UTC
Yeah, sorry for that.

*** This bug has been marked as a duplicate of bug 2013386 ***