Bug 703683

Summary:	anaconda creates wrongly named ifcfg scripts; impossible to start network on firstboot
Product:	[Fedora] Fedora	Reporter:	Matt Kinni <matt>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	anaconda-maint-list, 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-11 15:41:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Matt Kinni 2011-05-11 01:43:36 UTC

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 Chris Lumens 2011-05-11 15:41:55 UTC

This is due to biosdevname changing the naming scheme halfway through the release process.  Please test again with one of the final release candidates and let us know if you're continuing to see problems.  Thanks.

Comment 2 Matt Kinni 2011-05-18 23:51:27 UTC

It works great on the latest release candidate, thanks