My best guess would be that the device eth0 isn’t present. In newer releases, the kernel is naming the ethernet-devices differently. If you are running vmware, try ens192 or ens166 as device. But if you have only 1 interface, don’t supply the device at all.
Kind regards, Andreas Dijkman > On 9 May 2018, at 13:22, Kevin Olbrich <k...@sv01.de> wrote: > > The previous text was not displayed correctly: > network --device=eth0 --activate --onboot=on --bootproto=dhcp > > https://paste.fedoraproject.org/paste/FUFMmfAFbl08Tq~vi1spIA > <https://paste.fedoraproject.org/paste/FUFMmfAFbl08Tq~vi1spIA> > > > Mit freundlichen Grüßen / best regards, > Kevin Olbrich. > > 2018-05-09 13:18 GMT+02:00 Kevin Olbrich <k...@sv01.de <mailto:k...@sv01.de>>: > Hi! > > I have set up a kickstart profile for fedora 28 (first kickstart project). > My kickstart file contains: > network --device=eth0 --activate --onboot=on --bootproto=dhcp > > Every time I try deploying the image profile, I get: > Source http://xxx. <http://xxx./>.. needs network for installation. > (/tmp/anaconda.log) > > Both "installation source" and "software selection" are marked by exclamation > marks. > Network configuration is ticked and "wired eth0 connected". > > Any ideas? > > Kind regards > Kevin > > _______________________________________________ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
