Bug 354581

Summary:	doesn't choose the right network device to auto-start for live installs
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	9	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-08-04 14:26:35 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:

Description Bill Nottingham 2007-10-26 17:48:18 UTC

Description of problem:

On my box, I have two network cards. eth0 is disconnected while eth1 is
connected via NetworkManager.

anaconda, when doing a live install, always defaults eth0 to activate on boot.

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

rawhide-developer-20071025

Comment 1 Bug Zapper 2008-05-14 03:45:33 UTC

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Andy Lindeberg 2008-06-02 19:42:34 UTC

Does this persist in Fedora 9?