Bug 703684 - anaconda creates wrongly named ifcfg scripts; impossible to start network on firstboot
Summary: anaconda creates wrongly named ifcfg scripts; impossible to start network on ...
Keywords:
Status: CLOSED CURRENTRELEASE
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-05-11 01:45 UTC by Matt Kinni
Modified: 2011-05-11 15:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-11 09:31:26 UTC
Type: ---


Attachments (Terms of Use)
anaconda log (3.34 KB, text/plain)
2011-05-11 01:45 UTC, Matt Kinni
no flags Details
anaconda log2 (39.67 KB, text/plain)
2011-05-11 01:47 UTC, Matt Kinni
no flags Details
anaconda syscong (other 2 are .log and .ifcfg.log) (96.72 KB, text/plain)
2011-05-11 01:47 UTC, Matt Kinni
no flags Details

Description Matt Kinni 2011-05-11 01:45:21 UTC
Created attachment 498185 [details]
anaconda log

Description of problem:

After my netinstall anaconda created an ifcfg-pci10p1 network script, but the correct device name was actually ifcfg-p10p1. I had to find this name manually in /proc and rename the ifcfg script and edit the device name inside it.


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

How reproducible:
Always

Steps to Reproduce:
1. install fedora minimal 
2. system network start --> fails, complains of missing device
3.
  
Actual results:
cannot internet

Expected results:
internet

Additional info:
I don't know which specific anaconda logs are important but I'll try

Comment 1 Matt Kinni 2011-05-11 01:47:03 UTC
Created attachment 498186 [details]
anaconda log2

Comment 2 Matt Kinni 2011-05-11 01:47:53 UTC
Created attachment 498187 [details]
anaconda syscong (other 2 are .log and .ifcfg.log)

Comment 3 Radek Vykydal 2011-05-11 09:31:26 UTC
Thanks for the report.
This is because of using F15 Beta compose with "Updates Testing" repository
containing newer version of biosdevname. In F15 Test Candidate the problem is
gone as the compose contains the newer version of biosdevname (pXpY).


Note You need to log in before you can comment on or make changes to this bug.