Bug 621697

Summary: Systemd does not complete boot after yum upgrade from F13 to Rawhide
Product: [Fedora] Fedora Reporter: W. Michael Petullo <mike>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: lpoetter, metherid, mschmidt
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-05 22:13:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description W. Michael Petullo 2010-08-05 20:45:52 UTC
Description of problem:
Systemd does not complete boot after yum upgrade from F13 to Rawhide.

Version-Release number of selected component (if applicable):
systemd-sysvinit-5-2.fc15.x86_64

How reproducible:
Every time

Steps to Reproduce:
Try to boot
  
Actual results:
Boot hangs after starting all services (between last service and mingetty / X, I think). I am still trying to figure out how systemd boots, so I have not yet been able to pinpoint where in the process the system hangs.

Expected results:
System should boot

Additional info:
Adding init=/sbin/upstart results in the system booting fine.

Also, the following works:
1. Boot into single user mode
2. /etc/rc 5
3. gdm

Comment 1 Michal Schmidt 2010-08-05 21:51:22 UTC
I think you'll find that the post-install script of systemd-units-5-2 failed to enable the necessary services (getty, prefdm, ...) because systemctl segfaulted (bug 621200).

Use "yum history info systemd-units" to see if there was any unusual output from the scriptlet.

Comment 2 W. Michael Petullo 2010-08-05 22:13:46 UTC
Confirmed as the effects of bug #621200.

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