Description of problem: I'm getting this exception when enabling and disabling network interfaces in GUI. How reproducible: Always Steps to reproduce: 1) Start installation in GUI 2) Go to the Network spoke 3) Enable and disable network interface again and again Additional info: When the network interface is disabled you can't enable it again. In GUI the button looks enabled, however interface settings isn't loaded. Version-Release number of selected component: anaconda-26.21.3-1 The following was filed automatically by anaconda: anaconda 26.21.3-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/network.py", line 679, in on_device_off_toggled device.disconnect(None) GLib.GError: nm-device-error-quark: This device is not active (4) Additional info: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.11.0-0.rc6.git0.1.fc26.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 26 Potential duplicate: bug 1330506
Created attachment 1272897 [details] File: anaconda-tb
Created attachment 1272898 [details] File: environ
Created attachment 1272899 [details] File: lsblk_output
Created attachment 1272900 [details] File: nmcli_dev_list
Created attachment 1272901 [details] File: os_info
This error is happening only when you have 2 or more network interfaces and this behavior varies based on the number of network interfaces. When you have 3 network interfaces one of them is working correctly others have this issue... I'm experiencing this on Rawhide too.
I believe it will be fixed with bug 1443878.
Similar problem has been detected: Enable then disable then I think enable ethernet, then crash. addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/libexec/system-python /sbin/anaconda hashmarkername: anaconda kernel: 4.11.5-300.fc26.x86_64 package: anaconda-26.21.9-1 product: Fedora reason: GLib.GError: nm-device-error-quark: This device is not active (4) release: Cannot get release name. version: 26
Proposed as a Blocker for 26-final by Fedora user chrismurphy using the blocker tracking app because: I can't find an applicable release criterion, all the crashing ones have to do with partitioning. But it seems blocker worthy that the installer is crashing just by enabling/disabling ethernet.
Chris, do you have the full traceback from your reproduction of this? I ask because the fix for #1443878 (which Radek thought would fix this) landed in F26 a month ago...
Discussed at 2017-06-26 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2017-06-26/f26-blocker-review.2017-06-26-16.03.html . Rejected as a blocker, as it really doesn't violate any criteria, so far as we can tell; both reporters report that they had to turn an interface on, off, then on again to trigger the bug, thus you can certainly achieve anything network-related by just turning it on once and not messing around with it further (the bug doesn't seem to outright prevent any network operation from working). I'm almost sure we had enough explicit and implicit FE votes (assuming those who voted +1 blocker would vote +1 FE) to make this a freeze exception issue, but just to be sure, can blocker voters please state whether they vote +1 FE? I do.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.