Description of problem: Attempting an upgrade from F-12 (minimal install) using F-13-Alpha-RC2 fails (see bug#567878). While attempting to present the error handling dialog, we seem to hit another failure. This bug is intended to track the python-meh failure. Version-Release number of selected component (if applicable): * anaconda-13.29 How reproducible: * 2 out of 2 attempts Steps to Reproduce: 1. Follow steps in https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Update_Bootloader Actual results: 13:10:35 Please manually connect your vnc client to test1247.test.redhat.com:1 (10.10.10.247) to begin the install. Press <enter> for a shell 13:10:36 Starting graphical installation. Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/meh/handler.py", line 162, in <lambda> File "/usr/lib/python2.6/site-packages/meh/handler.py", line 107, in handleException File "/usr/lib/anaconda/gui.py", line 1085, in mainExceptionWindow ImportError: No module named ui.gui Expected results: * Present failure dialog Additional info: * If this problem were wide spread, I believe it would affect the Alpha release criteria (https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria). But this seems to be specific to upgrades, which is listed as a beta release criteria (https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria)
Dunno what's going on here - could be a problem specific to that we're stuck in an exception down in the rpm callback, which pdb kind of hates. My stack trace is missing lines and line numbers for all frames after we go into rpm. Anyway from pdb if I try to import meh it succeeds, whereas import meh.ui fails with "No module named ui". Attempting to import meh manually via the imputil module similarly fails.
Do you see this anymore?
(In reply to comment #2) > Do you see this anymore? This doesn't appear to be showing up anymore. We are hitting bug#568567 at the tail end of an upgrade. Not sure if that's before or after this would hit. We can close this now and reopen should the problem resurface.
I can't think of a good resolution for this. Not like it matters.