Bug 634337

Summary: systemd updated to 10-2.fc15 fails to bring up networking (and other units)
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
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, notting, plautrba
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-09-15 20:13:35 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:
Attachments:
Description Flags
boot log from booting with systemd-10-2.fc15 to level 3
none
boot log from booting with systemd-10-2.fc15 to level 5
none
for comparison boot log from booting with systemd-9-3.fc15 to level 5 none

Description Michal Jaegermann 2010-09-15 20:06:09 UTC 
Description of problem:

After an update to 10-2.fc (that includes systemd-units and systemd-sysvinit) networking is not brought up anymore.  There is a looong timeout on a failed attempt to bring back a loopback interface and it is downhill from there.  Another very long timeout, not recorded in a boot.log, occures with 
readahead-collect.service.  These messages show up but do not end up in boot.log:

init[1]: Unit readahead-collect.service entered failed state.
init[1]: rtkit-daemon.service operation timed out. Terminating.
init[1]: network.service operation timed out. 
init[1]: Unit network.service entered failed state.
init[1]: restorecond.service: control process exited, code=exited status=7
init[1]: Unit restorecond.service entered failed state.

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

How reproducible:
always

Additional info:
Booting with 'init=/sbin/upstart' makes a machine boot correctly (without downgrading any packages).  The other way work around the issue is to downgrade systemd packages to 9-3.fc15.

Although these

init[1]: Unit readahead-collect.service entered failed state.
init[1]: restorecond.service: control process exited, code=exited status=7
init[1]: Unit restorecond.service entered failed state.

show up with systemd-9-3.fc15 too there is no very long timeout on readahead-collect.service.  Besides I thought that "status=7" was suppsed to be "special" and this should be silent.  On my test system selinux is off so this particular failure is fully expected.
Comment 1 Michal Jaegermann 2010-09-15 20:07:36 UTC 
Created attachment 447560 [details]
boot log from booting with systemd-10-2.fc15 to level 3
Comment 2 Michal Jaegermann 2010-09-15 20:08:19 UTC 
Created attachment 447561 [details]
boot log from booting with systemd-10-2.fc15 to level 5
Comment 3 Michal Jaegermann 2010-09-15 20:09:48 UTC 
Created attachment 447562 [details]
for comparison boot log from booting with systemd-9-3.fc15 to level 5
Comment 4 Bill Nottingham 2010-09-15 20:13:35 UTC 

*** This bug has been marked as a duplicate of bug 630225 ***
Comment 5 Michal Jaegermann 2010-09-15 20:37:37 UTC 
(In reply to comment #4)
> 
> *** This bug has been marked as a duplicate of bug 630225 ***

What about new extra long timeout on readahead-collect.service?
Comment 6 Bill Nottingham 2010-09-15 21:00:26 UTC 
It very well  may be related to the same thing.