Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 78627

Summary: [RFE?] anaconda-ks network lines with multiple NICs
Product: [Retired] Red Hat Linux Reporter: Mike McLean <mikem>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-24 18:34:37 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 Mike McLean 2002-11-26 17:17:53 UTC
* -re1125.nightly

On a machine with two network cards, I selected only one network card to be
activated.  The resulting anaconda-ks had two network lines (is this even
allowed?), with no indication that one should not be activated on boot.

When there are two network lines, how does anaconda chose which one it will use
for its own network config during the install?  If both specify nameserver or
hostname, which one wins?

Can we add an option to the network command to indicate whether or not the
device should be enabled on boot?

Comment 1 Michael Fulbright 2003-08-25 21:27:50 UTC

Comment 2 Jeremy Katz 2006-04-24 18:34:37 UTC
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed).  If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.