Description of problem: Version-Release number of selected component: anaconda-23.16-1 Additional info: reporter: libreport-2.1.11 addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-23-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.2.0-0.rc3.git0.1.fc23.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 23 Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/__init__.py", line 847, in _on_continue_clicked nextAction.refresh() File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 336, in refresh self._createBox() File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 158, in _createBox spoke.initialize() File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/network.py", line 1449, in initialize self.network_control_box.initialize() File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/network.py", line 463, in initialize self.add_device_to_list(device) File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/network.py", line 721, in add_device_to_list dev_cfg = DeviceConfiguration(device=device) File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/network.py", line 244, in __init__ uuid = nm.nm_device_setting_value(device.get_iface(), "connection", "uuid") File "/usr/lib64/python3.4/site-packages/pyanaconda/nm.py", line 755, in nm_device_setting_value raise SettingsNotFoundError(name) pyanaconda.nm.SettingsNotFoundError: SettingsNotFoundError('enp0s20u2u2',) Potential duplicate: bug 1193062
Created attachment 1055231 [details] File: anaconda-tb
Created attachment 1055232 [details] File: anaconda.log
Created attachment 1055233 [details] File: backtrace
Created attachment 1055234 [details] File: description
Created attachment 1055235 [details] File: dnf.log
Created attachment 1055236 [details] File: dnf.rpm.log
Created attachment 1055237 [details] File: environ
Created attachment 1055238 [details] File: ifcfg.log
Created attachment 1055239 [details] File: lsblk_output
Created attachment 1055240 [details] File: nmcli_dev_list
Created attachment 1055241 [details] File: packaging.log
Created attachment 1055242 [details] File: program.log
Created attachment 1055243 [details] File: storage.log
Created attachment 1055244 [details] File: syslog
*** Bug 1227276 has been marked as a duplicate of this bug. ***
It should be fixed in new version now. If you want to test it here is the updates image. https://jkonecny.fedorapeople.org/redhat/fix-1245960-updates.img Thank you for your help Alexander.
*** Bug 1244738 has been marked as a duplicate of this bug. ***
Hi Poma, could you please in more detail describe (as steps to reproduce if possible) how you deleted the connection profile as you write in the bug 1244738 ?
Hey man, here itz: [liveuser@localhost ~]$ nmcli connection NAME UUID TYPE DEVICE Wired connection 1 52c11f63-2a75-497a-9586-68521fbce7e9 802-3-ethernet ens3 [liveuser@localhost ~]$ [liveuser@localhost ~]$ nmcli connection delete Wired\ connection\ 1 Connection 'Wired connection 1' (52c11f63-2a75-497a-9586-68521fbce7e9) successfully deleted. [liveuser@localhost ~]$ [liveuser@localhost ~]$ nmcli connection NAME UUID TYPE DEVICE [liveuser@localhost ~]$ [liveuser@localhost ~]$ liveinst /usr/sbin/setenforce: SELinux is disabled Starting installer, one moment... anaconda 23.17-1 for Fedora 24 (pre-release) started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2) * if the graphical installation interface fails to start, try again with the inst.text bootoption to start text installation * when reporting a bug add logs from /tmp as separate text/plain attachments 17:05:21 Not asking for VNC because we don't have a network Error in atexit._run_exitfuncs: Traceback (most recent call last): File "/sbin/anaconda", line 91, in exitHandler os.unlink(pidfile_path) FileNotFoundError: [Errno 2] No such file or directory: '/var/run/anaconda.pid' /usr/sbin/setenforce: SELinux is disabled
Created attachment 1055890 [details] pyanaconda.nm.SettingsNotFoundError: SettingsNotFoundError('ens3',) - anaconda 23.17-1 exception report
GitHub PR: https://github.com/rhinstaller/anaconda/pull/274
*** Bug 1252993 has been marked as a duplicate of this bug. ***
Update: tested today with rawhide-20150813 boot.iso and https://jkonecny.fedorapeople.org/redhat/fix2-1245960-updates.img Steps to reproduce: 1) Boot anaconda 2) While at the welcome spoke plug-in the USB networking device http://plugable.com/products/ud-160-a 3) Proceed further - anaconda warns about being a test release and then shows the main spoke Results: No crash. The networking device however was not recognized b/c the driver was not loaded automatically. After switching manually to tty2 and doing: # insmod asix # dhclient enp0s20u2u2 I had networking working. I'll open another bug for the driver not being loaded automatically.
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.