Bug 1330506

Created attachment 1150861 [details]
File: anaconda-tb

Created attachment 1150862 [details]
File: anaconda.log

Created attachment 1150863 [details]
File: dnf.log

Created attachment 1150864 [details]
File: dnf.rpm.log

Created attachment 1150865 [details]
File: environ

Created attachment 1150866 [details]
File: lsblk_output

Created attachment 1150867 [details]
File: nmcli_dev_list

Created attachment 1150868 [details]
File: os_info

Created attachment 1150869 [details]
File: program.log

Created attachment 1150870 [details]
File: storage.log

Created attachment 1150871 [details]
File: syslog

Created attachment 1150872 [details]
File: ifcfg.log

Created attachment 1150873 [details]
File: packaging.log

Similar problem has been detected:

Pressed the '+' button  on the 'Network & Host Name' page to add a second network interface. Had an 802.11n dongle plugged in that wasn't recognized. Will try again without the dongle plugged in.

addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-24 quiet
hashmarkername: anaconda
kernel:         4.5.2-302.fc24.x86_64
package:        anaconda-24.13.4-1
product:        Fedora
reason:         GLib.GError: nm-device-error-quark: This device is not active (4)
release:        Cannot get release name.
reproducible:   Not sure how to reproduce the problem
version:        24

Petr, did you unplug the cable after installer has started? That is the only way I was able to use to reproduce the bug, clicking to ON/OFF button quick enough before the UI is refreshed (button hidden).

Here is updates image (for the anaconda-24.13.4-1) with patch that fixed the problem for me:
https://rvykydal.fedorapeople.org/updates.onoffunplugged.img

(In reply to Radek Vykydal from comment #15)
> Petr, did you unplug the cable after installer has started? That is the only
> way I was able to use to reproduce the bug, clicking to ON/OFF button quick
> enough before the UI is refreshed (button hidden).
> 
> Here is updates image (for the anaconda-24.13.4-1) with patch that fixed the
> problem for me:
> https://rvykydal.fedorapeople.org/updates.onoffunplugged.img

Radek,

When I experienced this bug, the ethernet cable was not plugged into the computer when I ran the installer. It was then that pressing the ON/OFF button caused he failure. All while the cable was not attached to the computer.

Hope this helps.

Geoff

(In reply to Geoffrey Marr from comment #16)
> (In reply to Radek Vykydal from comment #15)
> > Petr, did you unplug the cable after installer has started? That is the only
> > way I was able to use to reproduce the bug, clicking to ON/OFF button quick
> > enough before the UI is refreshed (button hidden).
> > 
> > Here is updates image (for the anaconda-24.13.4-1) with patch that fixed the
> > problem for me:
> > https://rvykydal.fedorapeople.org/updates.onoffunplugged.img
> 
> Radek,
> 
> When I experienced this bug, the ethernet cable was not plugged into the
> computer when I ran the installer. It was then that pressing the ON/OFF
> button caused he failure. All while the cable was not attached to the
> computer.
> 
> Hope this helps.
> 
> Geoff

EDIT: 
When I experienced this bug, the ethernet cable was not plugged into the
computer when I ran the installer. It was then that pressing the '+'
button to add another network interface caused the failure. All while the cable was not attached to the
computer.

Geoffrey, thank you for the info. It would be great if you could reproduce the bug and attach installer log files (as individual text/plain attachments ideally) to the report. We need

/tmp/anaconda.log
/tmp/syslog
/tmp/ifcfg.log

I reproduced this with anaconda 24.13.4-1

Steps:
1. Run anaconda from netinst with ethernet cable plugged off
2. Go to networking spoke
3. I can see that Ethernet is unavailable, but there is On/Off button (turned to OFF)
4. Turn on the button. Nothing happens.
5. Turn it off again. Anaconda freeze and after few seconds (about 10) it falls.

It seems to me, that the On/Off button is there accidentally, because when I click on wifi connection and then I go back to Ethernet the button disappears.

I tried to plug in the cable, the Ethernet automatically switches on and I can turn it off and on repeatedly without any error. When I unplug the cable the button disappear. When I connect cable again it appears again.

So the only problem is when you start anaconda with cable plugged off that the button appears even though it shouldn't and turning it on and off again breaks things.

From users point of view. When this happened to me I tried to turned on the connection because I thought that the cable is plugged on, but when I realized that it isn't I turned it off again and when I wanted to configure wifi I realized that it is frozen.

If you need some logs I can upload them.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.