Bug 637101

Summary: Network service startup fails
Product: [Fedora] Fedora Reporter: Zdenek Kabelac <zkabelac>
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-24 16:26:25 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
Failing boot log from network.service start
none
Log from systemctl restart network.service none

Description Zdenek Kabelac 2010-09-24 09:47:52 UTC 
Description of problem:

I'm unable to make my network.service 'active' on boot time - systemd reports it always as 'failed' - (attached log from systemctl restart network.service - where it makes to 'active' state.

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

systemd-sysvinit-10-4.fc15.x86_64
systemd-units-10-4.fc15.x86_64
systemd-10-4.fc15.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Zdenek Kabelac 2010-09-24 09:49:40 UTC 
Created attachment 449379 [details]
Failing boot log from network.service start

Here is cut from boot log - as the whole log seems to quite mangled - let me know if you need to know more details
Comment 2 Zdenek Kabelac 2010-09-24 09:50:50 UTC 
Created attachment 449380 [details]
Log from systemctl restart network.service

This command seems to be able to make network service active
Comment 3 Bill Nottingham 2010-09-24 16:26:25 UTC 

*** This bug has been marked as a duplicate of bug 603225 ***
Comment 4 Bill Nottingham 2010-09-24 16:26:47 UTC 

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