Bug 78627 - [RFE?] anaconda-ks network lines with multiple NICs
[RFE?] anaconda-ks network lines with multiple NICs
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2002-11-26 12:17 EST by Mike McLean
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-24 14:34:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike McLean 2002-11-26 12:17:53 EST
* -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 17:27:50 EDT
Comment 2 Jeremy Katz 2006-04-24 14:34:37 EDT
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.

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