anaconda doesn't initialize network when installing from kickstart on media
Place a kickstart file (ks.cfg) on installation media.
Use following network settings:
network --bootproto=dhcp --activate
Add following to isolinux.cfg:
no network available
warn "'ksdevice=link' does nothing (it's the default behavior)"
^^ this is obviously *not* a default.
Setting ksdevice=link activates network on boot.
The warning message is wrong.
By default anaconda does not activate any network device if it is not needed in initramfs.
Adding --device=link to kickstart network command, ie:
network --bootproto=dhcp --activate --device=link
We might be able to fix this bug by assuming ksdevice=link, but we need to be careful here and check that this assumption doesn't introduce regressions breaking some other scenarios. Also, we'll need to look for a device with link in dracut environment in parse-kickstart.
I posted a patch for review. New behaviour:
1) fixed --device=link option
2) if --device is missing
a) use ksdevice boot option if set
b) assume --device=link if ksdevice is not set
3) keep possibility to configure only hostname without configuring a device, ie for
a) if ksdevice is present, configure the device with defaults
b) if not, just set the hostname, ie we don't assume --device=link in this case
*** Red HatBug 1253621 has been marked as a duplicate of this bug. ***
Proposed patches - https://github.com/rhinstaller/anaconda/pull/298
Yes, installation with updates.devicelink.img activates network.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.