Red Hat Bugzilla – Bug 623017
Trying to get network access and failing leads to error
Last modified: 2012-05-31 02:53:32 EDT
Description of problem:
If in Fedora 14 Alpha RC2 x86_64 you try to activate additional repositories you're asked to setup a network connection. I tried wlan0 first and failed (probably PEBKAC), then tried eth0 and failed (probably HW issue). So I canceled setting up the network and ended with an error popup which let me exit or debug. That got me the following message:
Version-Release number of selected component (if applicable):
- anaconda 14.15
- whatever is on the F14 Alpha RC2 DVD
Steps to Reproduce:
1. Go through the installation
2. Select the update repo
3. Try to activate wlan0 and fail (like wrong WPA2 passphrase) and cancel that
4. Try to activate eth0 and fail (like no cable or no ip from dhcp) and cancel that
5. Cancel network activation
Error popup to exit or debug
Updates repo deselected, being able to continue installation
After I chose debug and got that message in the tty, I was able to continue the installation.
Created attachment 438160 [details]
screenshot of the traceback
Created attachment 438165 [details]
cancel -> traceback
Thanks for the report.
The bug (traceback) can occurs when choosing [Cancel] in device selection dialog of stage 2 network enablement (see the screenshot).
Sending patch for review.
Created attachment 438179 [details]
the second traceback
After fixing the first traceback, second one (attached) occurs. This one is caused by the fact that we don't disable/remove temporarily added repo after failed network enablement, so next try ([Ok] in Edir Repository dialog) leads to duplicate repos error which manifests itself with the traceback instead of error message because bug #623080.
I am going to send a patch fixing also this issue in scope of this bug to anaconda-devel-list.
(In reply to comment #3)
> I am going to send a patch fixing also this issue in scope of this bug to
No, I'm going to open separate bug #623639 for the issue.
This if fixed in master in anaconda-14.15-1, after alpha release, I'll push to f14-branch.
(In reply to comment #5)
> This if fixed in master in anaconda-14.15-1
oops, anaconda-15.0-1 that will be
This should be fixed in anaconda-14.17-1 (F14 Beta).
Can't reproduce this with anaconda 14.19 (i.e. F14 Final TC1.1) anymore.