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:
Please attach the traceback and anaconda logs: /tmp/anaconda-tb-* /tmp/anaconda.log /tmp/syslog Thank you.
https://github.com/rhinstaller/anaconda/pull/1934
I think I was able to reproduce the issue - the cause of the crash is the unplugged device. It would be good to see the logs though to make sure I really hit the same issue.
(In reply to Radek Vykydal from comment #1) > Please attach the traceback and anaconda logs: > > /tmp/anaconda-tb-* > /tmp/anaconda.log > /tmp/syslog > > Thank you. I didn't see a /tmp/anaconda-tb-* log file, but the traceback itself is in the syslog.
Created attachment 1551963 [details] anaconda log
Created attachment 1551965 [details] syslog
Thank you for the logs, looking at them I can confirm we are seeing the same issue which should be fixed by the PR in comment #2.
anaconda-30.25.5-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e2e3cfdb2b
anaconda-30.25.5-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e2e3cfdb2b
anaconda-30.25.5-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.