Description of problem: Activated network and went back to the hub. Anaconda crashed. Version-Release number of selected component: anaconda-18.19 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.19 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 569, in kickstartNetworkData : if not ifcfg.get("ESSID"): : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 942, in apply : nd = kickstartNetworkData(hostname=hostname) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 108, in _runSpoke : action.apply() : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 323, in _on_spoke_clicked : self._runSpoke(spoke) :AttributeError: 'NoneType' object has no attribute 'get'
Created attachment 630501 [details] File: anaconda-tb
Created attachment 630502 [details] File: product
Created attachment 630503 [details] File: type
Created attachment 630504 [details] File: ifcfg.log
Created attachment 630505 [details] File: storage.log
Created attachment 630506 [details] File: version
Created attachment 630507 [details] File: environ
Created attachment 630508 [details] File: anaconda.log
Created attachment 630509 [details] File: syslog
Created attachment 630510 [details] File: hashmarkername
Created attachment 630511 [details] File: packaging.log
Created attachment 630512 [details] File: cmdline_file
Created attachment 630513 [details] File: release
Created attachment 630514 [details] File: program.log
testing re-entering network spoke after configuring wlan0 per bug 871132 Package: anaconda-18.19 OS Release: Fedora release 18-Beta-TC6
When using wired connection, anaconda did not crash with version 18.21 on smoke12 iso.
This looks to be wireless specific, from the traceback. It's trying to check something about the ESSID.
Radek, can you advise more on the circumstances of this bug? Does it look bad enough to be a Beta blocker?
Setup WPA2-Personal and connected to it. Clicked on Done to return to the hub. Anaconda crashed. Package: anaconda-18.21 OS Release: Fedora release 18
This concerns all cases when network is configured (brought up) in pre-hub network standalone spoke. Proposing as Beta blocker, fix coming soon.
I'm seeing this one too - it looks like it is trying to fetch ESSID even when there's no working network config at all, let alone a wireless one.
what triggers the 'pre-hub network standalone spoke' exactly? under what circumstances do you see that?
Disconnect wired-ethernet cable for instance. Or shut off your DHCP service. Anything so that network autoconfig won't work.
I doubt that's the whole story. Surely it also has to be in a context where network access is needed...e.g. you booted from a kernel/initramfs pair, or passed updates=(remote location) or ks=(remote location), or - possibly - just that you booted the netinst ISO...
Yeah, I'm using the netinst ISO. Isn't that pretty standard practice? It's certainly been my preferred way to install Fedora since F10 or so. Otherwise, you get to download a whole DVD (which you likely don't want everything on) and then *re* download a significant fraction of the same packages at your first "yum update".
Sure. It's just important that for blocker evaluation we have a precise understanding of the trigger conditions for a bug.
(In reply to comment #26) > Sure. It's just important that for blocker evaluation we have a precise > understanding of the trigger conditions for a bug. Let me recap a bit with use cases: DVD install, cable not plugged in -> pre-hub network spoke is present a) connect to wifi using AP containing spaces -> bug 869106 b) connect to wifi using AP without spaces or plug cable with dhcp in 1) visit network spoke from hub -> this bz 2) proceed without visiting network spoke from hub -> bug 866516 (bug 870684) DVD install, cable without DHCP plugged in -> no pre-hub network spoke (incorrect) - bug 871129 All the bugs mentioned above should be fixed in 19.22 (plus bug 871429).
Discussed at 2012-10-31 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-31/f18beta-blocker-review-6.2012-10-31-16.00.log.txt . This whole area is confusing and we weren't entirely sure of the impact of this bug, so we weren't confident in accepting it as a blocker, but we accept it as NTH as it clearly has an impact on the viability of network installs. We agreed to leave the blocker question open so it can be revisited if it becomes a problem, but our expectation is this fix will be in 18.22 and the issue will be rendered moot.
anaconda-18.22-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.22-1.fc18
Package anaconda-18.22-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.22-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17432/anaconda-18.22-1.fc18 then log in and leave karma (feedback).
anaconda-18.23-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.23-1.fc18
anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.24-1.fc18
Discussed at 2012-11-05 QA meeting acting as a blocker review meeting. We didn't try very hard to determine blocker status, as this ought to be fixed already, and since there have been no dupes with 18.22+ and Tom reported in another bug that his tests are generally working better, we think it probably is. Can those who could reproduce this bug test with Beta TC7 or later and confirm that it's fixed now? Thanks!
I can confirm that this is no longer a problem with TC7. I am able to even change networks with TC7 - go from wired to wireless or vice versa. No crashes to report.
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.25-1.fc18
Selecting SSID for wifi installation in anaconda, F18 TC6 Package: anaconda-18.19 OS Release: Fedora release 18-Beta-TC6
verified per comment #34.
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.26-1.fc18
Package anaconda-18.26-1.fc18, lorax-18.22-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.26-1.fc18 lorax-18.22-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17714/lorax-18.22-1.fc18,anaconda-18.26-1.fc18 then log in and leave karma (feedback).
Back to VERIFIED.
18.26 went stable. Closing. (Bodhi closing of bugs when updates go stable is currently broken).