Description of problem:

When attempting to create a kickstart that results in a machine resilient to network changes and issues, anaconda throws a traceback.

Version-Release number of selected component (if applicable):

Fedora 30 Server Beta

How reproducible:100%

Steps to Reproduce:

Boot with command line that enables kickstart and provides two named Ethernet interfaces (the named Ethernet interfaces may not matter, but it was in my environment so I include it here):

linuxefi /vmlinuz inst.stage2=hd:UUID=9fc1593d-7c28-4bba-8763-1207a899652b
    inst.ks=hd:UUID=9fc1593d-7c28-4bba-8763-1207a899652b
    ifname=lom0:24:5e:be:22:45:6b ifname=lom1:24:5e:be:22:45:6c inst.gpt quiet

Have kickstart with these network lines:

# Network information
network  --bootproto=static --device=lom0 --ethtool="autoneg on"
    --gateway=172.31.254.254 --ip=172.31.254.253
    --nameserver=172.31.255.253,172.31.254.254 --netmask=255.255.255.0
    --noipv6 --activate
network  --bootproto=dhcp --device=lom1 --noipv6 --activate
network  --hostname=ipa-mo.xsintricity.com

Actual results:

Traceback, failure to apply network proxy to None device.  Fedora 29 works.  It fails to activate the second network device, which is OK because there is no cable plugged in at the moment, and the device is just a backup after all, but the 30 installer croaks out.

Expected results:

System should have one interface that static configures to desired value, and one interface that autoconfigures, that way if the headless system needs to be plugged into a foreign network, the network will still come up as long as you switch the Ethernet cable to the second port

Additional info: