Bug 683245 - Anaconda doesn't properly enable/configure eth0 interface for minimum Fedora 14/15 installation
Summary: Anaconda doesn't properly enable/configure eth0 interface for minimum Fedora ...
Keywords:
Status: CLOSED DUPLICATE of bug 702261
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 21:59 UTC by Artem S. Tashkinov
Modified: 2011-05-23 16:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-05-23 16:28:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
First boot of Fedora 15 (27.04 KB, image/png)
2011-03-08 21:59 UTC, Artem S. Tashkinov 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.