Red Hat Bugzilla – Bug 60249
unhandled exception against anaconda just after packages complete installing
Last modified: 2007-04-18 12:40:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.16-22 i686)
Description of problem:
Product is Red Hat 7.2 Enigma-i386 from downloaded iso. I have also tried using
latest anaconda installer updates "update-disk-20020117.img" with same results.
Unhandled exception occured just after packages completed installing. The
exceptions text reccoomended reporting as bug against anaconda. Full text as
Traceback (innermost last):
File "/usr/bin/anaconda"l,ine 620, in ?
File "/usr/lib/anaconda/gui.py" line 350, in run
File "/usr/lib/anaconda/gui.py" line 778, in run
File "/usr/lib/python1.5/site-packages/gtk.py", line 2608, in
File "/usr/lib/anaconda/gui.py", line 497, in handleRenderCallback
File "/usr/lib/anaconda/iw/progress_gui.py", line 135, in renderCallback
File "/usr/lib/anaconda/gui.py", line 399, in nextClicked
File "/usr/lib/anaconda/dispatch.py", line 143, in gotoNext
File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
File "/usr/lib/anaconda/packages.py", line 744, in doPostInstall
File "/usr/lib/anaconda/iutil.py", line 94, in execWithRedirect
OSError:[Errno 2] No such file or directory
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Boot off installation CD (optional use of linux-updates)
2.Install via gui
3.when it finishes installing of packages...instant crapola.
Actual Results: Dude, read the description.
Expected Results: Should have finished post install and prompted for a
restart. Then I would be using Open NMS by now.
There should be a more complete traceback. Can you attach the entire thing?
Created attachment 46620 [details]
Anaconda traceback dump
This has all the symptoms of a corrupted package due to a bad CD. Have you
checked the md5sum of the discs against the values given by Red Hat?
Closing due to inactivity.
Closing due to inactivity - please reopen if you have additional comments to add
to this bug.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.