Description of problem: Basic installation of Workstation over network. Version-Release number of selected component: anaconda-23.19.10-1 The following was filed automatically by anaconda: anaconda 23.19.10-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.4/site-packages/pyanaconda/nm.py", line 756, in nm_device_setting_value raise SettingsNotFoundError(name) File "/usr/lib64/python3.4/site-packages/pyanaconda/network.py", line 1057, in <genexpr> for dev in nm.nm_devices() if nm.nm_device_type_is_ethernet(dev))): File "/usr/lib64/python3.4/site-packages/pyanaconda/network.py", line 1057, in disableIPV6 for dev in nm.nm_devices() if nm.nm_device_type_is_ethernet(dev))): File "/usr/lib64/python3.4/site-packages/pyanaconda/network.py", line 1133, in write_network_config disableIPV6(rootpath) File "/usr/lib64/python3.4/site-packages/pyanaconda/kickstart.py", line 1097, in execute network.write_network_config(storage, ksdata, instClass, iutil.getSysroot()) File "/usr/lib64/python3.4/site-packages/pyanaconda/install.py", line 89, in doConfiguration ksdata.network.execute(storage, ksdata, instClass) File "/usr/lib64/python3.4/threading.py", line 868, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 253, in run threading.Thread.run(self, *args, **kwargs) pyanaconda.nm.SettingsNotFoundError: SettingsNotFoundError('enp0s20u3i1',) Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz ip=172.18.92.101::172.18.92.65:255.255.255.192:ST0003.lc.digifarma.nl::off noipv6 nameserver=172.18.92.65 inst.stage2=hd:UUID=e8507ec4-a731-44e5-8e24-729e418227e3 executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.2.3-300.fc23.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 23
Created attachment 1104800 [details] File: anaconda-tb
Created attachment 1104801 [details] File: anaconda.log
Created attachment 1104802 [details] File: dnf.log
Created attachment 1104803 [details] File: dnf.rpm.log
Created attachment 1104804 [details] File: environ
Created attachment 1104805 [details] File: lsblk_output
Created attachment 1104806 [details] File: nmcli_dev_list
Created attachment 1104807 [details] File: os_info
Created attachment 1104808 [details] File: storage.log
Created attachment 1104809 [details] File: syslog
Created attachment 1104810 [details] File: ifcfg.log
Created attachment 1104811 [details] File: packaging.log
Created attachment 1104812 [details] File: program.log
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.