Bug 200965 - network kickstart on multiple cards doesn't work
network kickstart on multiple cards doesn't work
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2006-08-01 16:37 EDT by Bill Nottingham
Modified: 2014-03-16 23:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-01 16:50:17 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 Bill Nottingham 2006-08-01 16:37:55 EDT

I have two network cards; I boot with:

linux ks=

The loader asks me which network device; I choose 'eth1'. It sets it up, grabs
the kickstart file, but then fails to mount the NFS share.

some log messages:

INFO: kickstartFroMNfs
INFO: results of nfs, host is curly.devel.redhat.com, dir is
opts are '(null)'
INFO: need to set up networking
INFO: going to pick interface
INFO: going to getNetConfig
INFO: dnsservers is
INFO: doing kickstart... setting it up
WARNING: no network link detected on eth0

It appears that it's trying to do the NFS over eth0, which is not plugged in.

I do have network --blah blah eth0 in my ks file, but that shouldn't affect the
Comment 1 Bill Nottingham 2006-08-01 16:50:17 EDT
Apparently, this is expected behavior if your network lines don't include your
ks device.

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