+++ This bug was initially created as a clone of Bug #623017 +++
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.
--- Additional comment from firstname.lastname@example.org on 2010-08-11 07:22:13 EDT ---
Created an attachment (id=438160)
screenshot of the traceback
--- Additional comment from email@example.com on 2010-08-11 07:45:08 EDT ---
Created an attachment (id=438165)
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.
--- Additional comment from firstname.lastname@example.org on 2010-08-11 08:48:56 EDT ---
Created an attachment (id=438179)
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.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
For rhel, I want to address the two issues from original bug separately, so only the first traceback is relevant for this bug. The issue is:
Selecting [Cancel] in stage 2 network enablement dialog causes traceback
And this is the fix - should be safe and isolated:
diff --git a/iw/network_gui.py b/iw/network_gui.py
index ecd010b..4188cc5 100644
@@ -185,7 +185,7 @@ def selectInstallNetDeviceDialog(network, devices = None):
rc = dialog.run()
if rc in [gtk.RESPONSE_CANCEL, gtk.RESPONSE_DELETE_EVENT]:
- retval = None
+ install_device = None
active = combo.get_active_iter()
install_device = combo.get_model().get_value(active, 1)
Thanks Bill, should be fixed in anaconda-13.21.75-1.
Trying to reproduce this with the 0730.5 tree I did the following:
1) Start an install from http
2) After stage2 has started switch to tty2 and do
- ifconfig eth0 down
- rm /etc/sysconfig/network-scripts/ifcfg-eth0
3) Proceed with installation
4) Just before package selection anaconda pops up a dialog telling you that you have to activate networking and eth0 is preselected in this dialog.
5) Click Cancel on this dialog without trying to activate the network. The traceback below happens:
anaconda 13.21.66 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/iw/network_gui.py", line 194, in selectInstallNetDeviceDialog
File "/usr/lib/anaconda/gui.py", line 979, in enableNetwork
File "/usr/lib/anaconda/yuminstall.py", line 1232, in doBackendSetup
if not anaconda.intf.enableNetwork():
File "/usr/lib/anaconda/backend.py", line 285, in doBackendSetup
if anaconda.backend.doBackendSetup(anaconda) == DISPATCH_BACK:
File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
File "/usr/lib/anaconda/gui.py", line 1426, in setScreen
File "/usr/lib/anaconda/gui.py", line 1339, in nextClicked
File "/usr/lib/anaconda/gui.py", line 1476, in keyRelease
UnboundLocalError: local variable 'install_device' referenced before assignment
Just to clarify the traceback from comment #7 is the same as on the screenshot from the original bug report.
Now trying the same steps to reproduce with the 0818.0 tree I got the network activation dialog again. After clicking Cancel there's an error dialog:
Some of your repositories require networking,
but there was an error enabling the network on your
Moving to VERIFIED.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.