Bug 740674

Summary: fc16 beta netinst on p1p1 has no network after reboot.
Product: [Fedora] Fedora Reporter: Jerry Amundson <jamundso>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, awilliam, iarlyy, jonathan, notting, plautrba, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-23 18:32:22 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
install.log
none
messages none

Description Jerry Amundson 2011-09-22 21:46:26 UTC 
Description of problem:
fc16 beta netinst on p1p1 has no network after reboot.

Version-Release number of selected component (if applicable):
Fedora 16 Beta Netinst

How reproducible:
always

Steps to Reproduce:
1. Install from netinst on system with em1 and p1p1
2. reboot
3.
  
Actual results:
no network - i had to login and "ifup p1p1"

Expected results:
network on p1p1 automatically

Additional info:
Comment 1 Jerry Amundson 2011-09-23 17:34:47 UTC 
Created attachment 524663 [details]
install.log
Comment 2 Jerry Amundson 2011-09-23 17:35:40 UTC 
I haven't found what the actual problem is, so I'm unsure which component to select.
Comment 3 Jerry Amundson 2011-09-23 17:46:47 UTC 
Created attachment 524664 [details]
messages
Comment 4 Jerry Amundson 2011-09-23 17:54:27 UTC 
::::::::::::::
/etc/sysconfig/network-scripts/ifcfg-em1
::::::::::::::
DEVICE="em1"
HWADDR="00:06:5B:F7:B6:1D"
ONBOOT="no"
NM_CONTROLLED="yes"
::::::::::::::
/etc/sysconfig/network-scripts/ifcfg-p1p1
::::::::::::::
DEVICE="p1p1"
HWADDR="00:04:75:E1:A4:29"
BOOTPROTO="dhcp"
ONBOOT="yes"
NM_CONTROLLED="yes"
Comment 5 Bill Nottingham 2011-09-23 18:32:22 UTC 
Try 'systemctl enable network.service'.

*** This bug has been marked as a duplicate of bug 702261 ***
Comment 6 Adam Williamson 2011-10-13 18:29:47 UTC 

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