Bug 683245

Summary: Anaconda doesn't properly enable/configure eth0 interface for minimum Fedora 14/15 installation
Product: [Fedora] Fedora Reporter: Artem S. Tashkinov <aros>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: jonathan, 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-05-23 16:28:17 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
First boot of Fedora 15 none

Description Artem S. Tashkinov 2011-03-08 21:59:40 UTC
Created attachment 483038 [details]
First boot of Fedora 15

Description of problem: after booting eth0/pciXpY interface is not activated


Version-Release number of selected component (if applicable): Fedora 14/15 default


How reproducible: always


Steps to Reproduce:
1. Install minimum Fedora 14/15 installation
2. Set eth0/pciXpY interface enabled in anaconda during installation, leave everything else intact
3. Reboot
  
Actual results: check eth0/pciXpY status - it'll be down


Expected results: eth0/pciXpY status up


Additional info:

Comment 1 Artem S. Tashkinov 2011-03-08 22:07:31 UTC
I know

chkconfig --level 35 network on

solves this problem, but I cannot get why I need to tinker with the system to get the network up and running when I explicitly enabled it during installation.

Comment 2 Radek Vykydal 2011-05-23 16:28:17 UTC

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