Bug 949002

Summary: anaconda crashes while trying to select wireless network
Product: [Fedora] Fedora Reporter: Tom Lane <tgl>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, awilliam, g.kaviyarasu, hhorak, jonathan, mkolman, rvykydal, satellitgo, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: RejectedFreezeException
Fixed In Version: anaconda-19.21-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-30 04:37:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda traceback none

Description Tom Lane 2013-04-05 15:51:38 UTC 
Description of problem:
Trying to install F19 Alpha TC5 (also happened with TC4) in an environment where only available network is a password-protected wireless net.

Version-Release number of selected component (if applicable):
whatever's in TC5

How reproducible:
it fails here about four out of five times, but it did work once for unclear reasons

Steps to Reproduce:
1. at network config screen, click on wireless card
2. select protected network from drop-down dialog box
  
Actual results:
popup with "an unknown error has occurred"

Expected results:
should be able to configure network addressing & password at this point

Additional info:
I can't figure out how to copy-and-paste the stack trace, but it looks like it's trying to update the hostname and is unable to cope with the fact that it can't connect yet.
Comment 1 Tom Lane 2013-04-05 16:05:15 UTC 
On my sixth try, I got past this by the expedient of manually entering a hostname (in the text box for that) before attempting to configure the wireless.  But I'm not sure if this actually prevented the broken lookup attempt, or if it just randomly worked this time.  Anyway, that's a possible workaround for others seeing a crash at this point.
Comment 2 Chris Lumens 2013-04-05 17:01:29 UTC 
You can use the automated bug reporting thing to report bugs, in which case the traceback will be posted for you.  Or, you can switch over to a tty and grab /tmp/anaconda-tb-* and attach it to this bug.
Comment 3 Tom Lane 2013-04-05 18:23:30 UTC 
Created attachment 731986 [details]
anaconda traceback
Comment 4 Tom Lane 2013-04-05 18:25:49 UTC 
thanks, I'd forgotten about the /tmp file.

Also, after trying it several more times, I'm now pretty confident in stating that entering a hostname manually before configuring the card *does* suppress the problem.
Comment 5 satellitgo 2013-04-05 20:34:42 UTC 
dd USB boot - acer aspire one n450 2 GB Memory: no wired network connected. Tried to configure wireless WEP on initial spoke that appears when no networking detected; and anaconda 19.16-1 in TC5 crashed. Only resort was to quit
Comment 6 Adam Williamson 2013-04-05 21:09:25 UTC 
Proposing as Alpha freeze exception; probably not blocker-worthy as it's only wireless and there's a workaround, but seems like a good FE candidate.
Comment 7 Tom Lane 2013-04-05 22:56:07 UTC 
(In reply to comment #6)
> ... probably not blocker-worthy as it's only wireless ...

My guess is that it's not just wireless but any case where manual configuration is needed for connectivity, eg wired network without DHCP server.  Protected wireless is probably just the most common case.
Comment 8 Radek Vykydal 2013-04-08 10:57:48 UTC 
I am not able to reproduce. It would be great if you could try this updates image with a patch:

http://rvykydal.fedorapeople.org/updates.949002.img

You can copy it to storage (eg USB disk) and use

updates=hd:<DEVICE_NAME>:<PATH_TO_THE_FILE>

(eg updates=hd:sdc1:/updates.949002.img)

boot option.
Comment 9 Adam Williamson 2013-04-15 16:49:42 UTC 
Discussed at 2013-04-15 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-15/f19alpha-blocker-review-7.2013-04-15-16.00.log.txt . Rejected as an FE for Alpha: it's just too late to be taking an as-yet-untested fix for a not-super-critical issue.
Comment 10 Fedora Update System 2013-04-23 01:38:16 UTC 
anaconda-19.21-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/anaconda-19.21-1.fc19
Comment 11 Fedora Update System 2013-04-23 03:00:09 UTC 
Package anaconda-19.21-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-19.21-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-6338/anaconda-19.21-1.fc19
then log in and leave karma (feedback).
Comment 12 Fedora Update System 2013-04-24 16:37:18 UTC 
Package anaconda-19.21-1.fc19, python-meh-0.23-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-19.21-1.fc19 python-meh-0.23-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-6338/python-meh-0.23-1.fc19,anaconda-19.21-1.fc19
then log in and leave karma (feedback).
Comment 13 Fedora Update System 2013-04-30 04:37:35 UTC 
anaconda-19.21-1.fc19, python-meh-0.23-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.